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

From: Steven Haigh <netwiz@crc.id.au>
To: xen-devel@lists.xenproject.org, jgross@suse.com
Cc: luwei.kang@intel.com, wl@xen.org, andrew.cooper3@citrix.com,
	marmarek@invisiblethingslab.com, olekstysh@gmail.com,
	paul.durrant@citrix.com, JBeulich@suse.com, puwen@hygon.cn,
	roger.pau@citrix.com, Volodymyr_Babchuk@epam.com,
	chao.gao@intel.com
Subject: Re: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update
Date: Sun, 29 Sep 2019 00:07:43 +1000	[thread overview]
Message-ID: <1569679663.2427.0@crc.id.au> (raw)
In-Reply-To: <20190928050923.23540-1-jgross@suse.com>

At the risk of sounding like a broken record, is there an progress with 
investigations on the AMD Ryzen 3xxx series and Windows HVM systems?
Steven Haigh

📧 netwiz@crc.id.au     💻 https://www.crc.id.au
📞 +613 9001 6090       📱 +614 1293 5897

On Sat, Sep 28, 2019 at 07:09, Juergen Gross <jgross@suse.com> wrote:
> As multiple rather important patch series are very short before being 
> ready
> I have decided to push the hard code freeze one week back to October 
> 4th.
> 
> 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
> ---> We are here
> * Hard code freeze: October 4th, 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?
> 
> = Projects =
> 
> == Hypervisor ==
> 
> *  Core scheduling (v4)
>   -  Juergen Gross
> 
> === x86 ===
> 
> *  Intel Processor Trace virtualization enabling (v1)
>   -  Luwei Kang
> 
> *  Linux stub domains (RFC v2)
>   -  Marek Marczykowski-Górecki
> 
> *  Improve late microcode loading (v12)
>   -  Chao Gao
> 
> *  Fixes to #DB injection
>   -  Andrew Cooper
> 
> *  CPUID/MSR Xen/toolstack improvements
>   -  Andrew Cooper
> 
> *  Improvements to domain_crash()
>   -  Andrew Cooper
> 
> *  EIBRS
>   -  Andrew Cooper
> 
> *  Xen ioreq server (v2)
>   -  Roger Pau Monne
> 
> === ARM ===
> 
> == 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
> 
> *  add per-domain IOMMU control
>   -  Paul Durrant
> 
> *  TEE mediator (and OP-TEE) support in XEN
>   -  Volodymyr Babchuk
> 
> *  Renesas IPMMU-VMSA support + Linux's iommu_fwspec
>   -  Oleksandr Tyshchenko
> 
> 
> Juergen Gross
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel

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