[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ANNOUNCE] Xen 4.15 release schedule and feature tracking

  • To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Fri, 15 Jan 2021 10:43:58 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5De1qY0lwHLnuidj1GWz4kXY7GUHbDjrrmrJivEsFZQ=; b=I3sByjpGRvVNb4P1g3NjpadbGZJXsekTOe4o7TpOksIdqdgvOyLLCbue/vK1TETJWtnIJ7ZMzqNzn3uxGNCcCS291VKQbUodD/MyhkMBFWJ+SxuyNUmDE6ea67131g/TR32y724WOAE01DkF9Lb4/GXoxBEdEc9sHSfYKsLdUZ623PZfaNhaxOb64d9kzkMXMP6S93kKsJL4ubRLRLSp8qDcTCHmLLwrSdcGPOi21dilkgVWN6pwE5dDtnKkK/PTc0EpVqBpTAHXNeUTCQEyR2m5ggYU6FqdFknbxLd+rvIruPE2H35LVlvi8APk1eD8DL9D2PnMyYh4tYqHNnKSLg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lpoquDHt3q/Kx8PQ9Xsa5ClT7BmOMUlZZJc/Xo5/hufDZtnbLkJlSllBYddk4JzyLlk8d/bfrm8eMGdDAJFdaTQhVssW8uhC1Xn+9OM7vvH1Qwehs/J13/dycHuBW/TL1RsIHcKW+0hPz1Bg4TDZV5MS1xbta0vNSK8ByXZGN9JBWt15DlLDDhlqueEDD+hbDXUwZ7/ZDpSHt3OEA3mTlhnFxeZdunyX5QHhlOEtP9AFIN9Gc9trqbRpOdULHQSQWyDGN6aKwAwSBVa0JBQDXuuETQ6yEjZeS6vADtI/KdZSSiqE7I+O3pvtrNdhHvec7OYUCsozPoHPlt6EJO9rzQ==
  • Authentication-results-original: citrix.com; dkim=none (message not signed) header.d=none;citrix.com; dmarc=none action=none header.from=arm.com;
  • Cc: Ian Jackson <iwj@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "committers@xxxxxxxxxxxxxx" <committers@xxxxxxxxxxxxxx>, Tamas K Lengyel <tamas@xxxxxxxxxxxxx>, Michał Leszczyński <michal.leszczynski@xxxxxxx>
  • Delivery-date: Fri, 15 Jan 2021 10:44:40 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: citrix.com; dkim=none (message not signed) header.d=none;citrix.com; dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHW5QJrM06mM8kmgkKihyk9gkB60aonVGsAgAAxGgCAAQcdgA==
  • Thread-topic: [ANNOUNCE] Xen 4.15 release schedule and feature tracking


> On 14 Jan 2021, at 19:02, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote:
> On 14/01/2021 16:06, Ian Jackson wrote:
>> The last posting date for new feature patches for Xen 4.15 is
>> tomorrow. [1]  We seem to be getting a reasonable good flood of stuff
>> trying to meet this deadline :-).
>> Patches for new fetures posted after tomorrow will be deferred to the
>> next Xen release after 4.15.  NB the primary responsibility for
>> driving a feature's progress to meet the release schedule, lies with
>> the feature's proponent(s).
>>  As a reminder, here is the release schedule:
>> + (unchanged information indented with spaces):
>>   Friday 15th January    Last posting date
>>       Patches adding new features should be posted to the mailing list
>>       by this cate, although perhaps not in their final version.
>>   Friday 29th January    Feature freeze
>>       Patches adding new features should be committed by this date.
>>       Straightforward bugfixes may continue to be accepted by
>>       maintainers.
>>   Friday 12th February **tentatve**   Code freeze
>>       Bugfixes only, all changes to be approved by the Release Manager.
>>   Week of 12th March **tentative**    Release
>>       (probably Tuesday or Wednesday)
>>  Any patches containing substantial refactoring are to treated as
>>  new features, even if they intent is to fix bugs.
>>  Freeze exceptions will not be routine, but may be granted in
>>  exceptional cases for small changes on the basis of risk assessment.
>>  Large series will not get exceptions.  Contributors *must not* rely on
>>  getting, or expect, a freeze exception.
>> + New or improved tests (supposing they do not involve refactoring,
>> + even build system reorganisation), and documentation improvements,
>> + will generally be treated as bugfixes.
>>  The codefreeze and release dates are provisional and will be adjusted
>>  in the light of apparent code quality etc.
>>  If as a feature proponent you feel your feature is at risk and there
>>  is something the Xen Project could do to help, please consult me or
>>  the Community Manager.  In such situations please reach out earlier
>>  rather than later.
>> In my last update I asked this:
>>> If you are working on a feature you want in 4.15 please let me know
>>> about it.  Ideally I'd like a little stanza like this:
>>> S: feature name
>>> O: feature owner (proponent) name
>>> E: feature owner (proponent) email address
>>> P: your current estimate of the probability it making 4.15, as a %age
>>> But free-form text is OK too.  Please reply to this mail.
>> I received one mail.  Thanks to Oleksandr Andrushchenko for his update
>> on the following feeature:
>>  IOREQ feature (+ virtio-mmio) on Arm
>>  https://www.mail-archive.com/xen-devel@xxxxxxxxxxxxxxxxxxxx/msg87002.html
>>  Julien Grall <julien@xxxxxxx>
>>  Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
>> I see that V4 of this series was just posted.  Thanks, Oleksandr.
>> I'll make a separate enquiry about your series.
>> I think if people don't find the traditional feature tracking useful,
>> I will try to assemble Release Notes information later, during the
>> freeze, when fewer people are rushing to try to meet the deadlines.
> (Now I have working email).
> Features:
> 1) acquire_resource fixes.
> Not really a new feature - entirely bugfixing a preexisting one.
> Developed by me to help 2).  Reasonably well acked, but awaiting
> feedback on v3.
> 2) External Processor Trace support.
> Development by Michał.  Depends on 1), and awaiting a new version being
> posted.
> As far as I'm aware, both Intel and CERT have production systems
> deployed using this functionality, so it is very highly desirable to get
> into 4.15.
> 3) Initial Trenchboot+SKINIT support.
> I've got two patches I need to clean up and submit which is the first
> part of the Trenchboot + Dynamic Root of Trust on AMD support.  This
> will get Xen into a position where it can be started via the new grub
> "secure_launch" protocol.
> Later patches (i.e. post 4.15) will do support for Intel TXT (i.e.
> without tboot), as well as the common infrastructure for the TPM event
> log and further measurements during the boot process.
> 4) "simple" autotest support.

5) SMMU-v3 Support from Rahul Singh

See "xen/arm: Add support for SMMUv3 driver”

Almost everything in the serie is already acked.


> Bugs:
> 1) HPET/PIT issue on newer Intel systems.  This has had literally tens
> of reports across the devel and users mailing lists, and prevents Xen
> from booting at all on the past two generations of Intel laptop.  I've
> finally got a repro and posted a fix to the list, but still in progress.
> 2) "scheduler broken" bugs.  We've had 4 or 5 reports of Xen not
> working, and very little investigation on whats going on.  Suspicion is
> that there might be two bugs, one with smt=0 on recent AMD hardware, and
> one more general "some workloads cause negative credit" and might or
> might not be specific to credit2 (debugging feedback differs - also
> might be 3 underlying issue).
> All of these have had repeated bug reports.  I'd classify them as
> blockers, given the impact they're having on people.
> ~Andrew



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.