Re: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update

[Roman Shaposhnik <roman@xxxxxxxxxx>]

On Thu, Aug 1, 2019 at 9:01 AM Juergen Gross <jgross@xxxxxxxx> wrote:
>
> This email only tracks big items for xen.git tree. Please reply for items you
> would like to see in 4.13 so that people have an idea what is going on and
> prioritise accordingly.
>
> You're welcome to provide description and use cases of the feature you're
> working on.
>
> = Timeline =
>
> We now adopt a fixed cut-off date scheme. We will release about every 8 
> months.
> The upcoming 4.13 timeline are as followed:
>
> * Last posting date: September 13th, 2019
> * Hard code freeze: September 27th, 2019
> * RC1: TBD
> * Release: November 7th, 2019
>
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.13 must be posted initially no later than the
> last posting date and finally no later than the hard code freeze. All
> patches posted after that date will be automatically queued into next
> release.
>
> RCs will be arranged immediately after freeze.
>
> We recently introduced a jira instance to track all the tasks (not only big)
> for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.
>
> Some of the tasks tracked by this e-mail also have a corresponding jira task
> referred by XEN-N.
>
> I have started to include the version number of series associated to each
> feature. Can each owner send an update on the version number if the series
> was posted upstream?

Great timeline! On LF Edge Project EVE side, we'd like to help with testing an
upcoming 4.13 as much as we can. The goal for us is to get rid of out-of-tree
patches (most of them have to do with Alpine Linux support) and to make sure
that we don't have issue on any of these platforms:
     https://wiki.lfedge.org/display/EVE/Hardware+Platforms+Supporting+EVE

Since I'm still a little bit new to how Xen release process works, I'm wondering
what's the best way for us to stay on the same page with the rest of
the community
testing efforts?

Will there be nightly tarballs published at some point? Is there any
kind of build
infrastructure I can hook up on our side to make sure that I report issues as
soon as possible?

Thanks,
Roman.

>
> = Projects =
>
> == Hypervisor ==
>
> *  Per-cpu tasklet
>   -  XEN-28
>   -  Konrad Rzeszutek Wilk
>
> *  Improvements to domain creation (v2)
>   -  Andrew Cooper
>
> *  Core aware scheduling (RFC v1)
>   -  Dario Faggioli
>
> *  Core aware scheduling for credit2 (RFC v1)
>   -  Dario Faggioli
>
> *  Core scheduling (v1)
>   -  Juergen Gross
>
> *  Switch to use domheap page for page table (RFC v1)
>   -  Wei Liu
>
> === x86 ===
>
> *  PV-IOMMU (v7)
>   -  Paul Durrant
>
> *  HVM guest CPU topology support (RFC)
>   -  Chao Gao
>
> *  Intel Processor Trace virtualization enabling (v1)
>   -  Luwei Kang
>
> *  Linux stub domains (RFC v2)
>   -  Marek Marczykowski-Górecki
>
> *  Improve late microcode loading (v8)
>   -  Chao Gao
>
> *  Fixes to #DB injection
>   -  Andrew Cooper
>
> *  CPUID/MSR Xen/toolstack improvements
>   -  Andrew Cooper
>
> *  Improvements to domain_crash()
>   -  Andrew Cooper
>
> *  EIBRS
>   -  Andrew Cooper
>
> === ARM ===
>
> *  TEE mediator (and OP-TEE) support in XEN (v7)
>   -  Volodymyr Babchuk
>
> == Completed ==
>
> *  Drop tmem
>   -  Wei Liu
>
> *  Add support for Hygon Dhyana Family 18h processor
>   -  Pu Wen
>
> *  hypervisor x86 instruction emulator additions for AVX512
>   -  Jan Beulich
>
> *  x2APIC support for AMD
>   -  Jan Beulich
>
>
> Juergen Gross
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel