Re: Xen 4.18 release: Reminder about code freeze

[Henry Wang <Henry.Wang@xxxxxxx>]

Hi Jan,

> On Sep 26, 2023, at 15:46, Jan Beulich <jbeulich@xxxxxxxx> wrote:
> 
> On 25.09.2023 09:24, Jan Beulich wrote:
>> On 25.09.2023 03:25, Henry Wang wrote:
>>> Hi everyone,
>>> 
>>> This is the reminder that we are currently in code freeze. The hard code
>>> freeze date will be in two weeks, i.e. Fri Oct 6, 2023.
>>> 
>>> The planned date for 4.18 rc1 is this Friday, i.e. Sep 29, 2023.
>>> 
>>> Also, below is the (updated) critical items on my list for 4.18 release:
>>> 1. [PATCH 0/7] tools: More Python 3 fixes (part 1 of N)
>>> https://gitlab.com/xen-project/xen/-/issues/114
>>> 
>>> 2. tools: Switch to non-truncating XENVER_* ops
>>> https://lore.kernel.org/xen-devel/20230117135336.11662-1-andrew.cooper3@xxxxxxxxxx/
>>> 
>>> 3. dom0less vs xenstored setup race Was: xen | Failed pipeline for staging 
>>> | 6a47ba2f
>>> https://marc.info/?l=xen-devel&m=168312468808977
>>> https://marc.info/?l=xen-devel&m=168312687610283
>>> 
>>> 4. [PATCH v2 0/8] Fixes to debugging facilities
>>> https://lore.kernel.org/xen-devel/21cc28b9-91d1-1e6e-23ac-00c44f3ec08e@xxxxxxxxx/
>> 
>> May I ask that at least "x86: support data operand independent timing mode"
>> also be put on this list? There were other x86 items we wanted in 4.18, but
>> I think they have been put on hold now for too long to still be reasonable
>> to expect to make it.
> 
> On the x86 maintainers meeting yesterday two more feature series (i.e. leaving
> aside big fixes) were identified as candidates to also add to the tracking
> list:
> 
> - runstate/time area registration by (guest) physical address
> - annotate entry points with type and size

Added.

> 
> Furthermore may I ask that you keep an eye on the physical CPU hotplug
> situation? It continues to be documented as fully supported, and as long as
> that's the case 47342d8f490c (" x86/ACPI: Ignore entries with invalid APIC IDs
> when parsing MADT") would imo need reverting. While I had indicated that I
> would do the revert, a patch to SUPPORT.md was meanwhile proposed (which
> would of course further need accompanying by a CHANGELOG.md entry), but didn't
> really make progress since then. Yet I also didn't want to "needlessly" do the
> revert ...

I think you are referring to [1] (and a proper CHANGELOG), I added this to my 
list
if all people involved is fine with this patch from Stefano, we can commit this 
one for
SUPPORT.md and I can probably send a patch for CHANGELOG.

[1] 
https://lore.kernel.org/xen-devel/alpine.DEB.2.22.394.2309111534030.1847660@ubuntu-linux-20-04-desktop/

Kind regards,
Henry

> 
> Jan