|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [ANNOUNCE] Xen 4.15 release schedule and feature tracking
Hi, > 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” https://lists.xenproject.org/archives/html/xen-devel/2021-01/msg00429.html Almost everything in the serie is already acked. Cheers Bertrand > > > 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 |