On Thu, Nov 21, 2019 at 09:53:44AM +0100, Jan Beulich wrote: > On 21.11.2019 07:05, Jürgen Groß wrote: > > Where do we stand with Xen 4.13 regarding blockers and related patches? > > > > 1. OSStest failure regarding nested test: > > I'm not quite sure whether the currently debated patch of Andrew is > > fixing the problem. If not, do we know what is missing or how to > > address the issue? If yes, could we please come to an agreement? > > As an alternative: any thoughts about ignoring this test failure for > > 4.13-RC3 (IOW: doing a force push)? > > I'd recommend against doing so, in particular seeing that all stable > trees are also affected. > > Andrew's patch may end up being a prereq to the full fix, but this > looks to not be entirely clear yet at this point. (I'm having a > hard time seeing a fair solution without this change.) > > > 2. Ryzen/Rome failures with Windows guests: > > What is the currently planned way to address the problem? Who is > > working on that? > > > > 3. Pending patches for 4.13: > > Could I please have feedback which patches tagged as "for-4.13" are > > fixing real regressions or issues? I don't want to take any patches > > not fixing real problems after RC3, and I hope to be able to get a > > push rather sooner than later to be able to let Ian cut RC3. > > According to my list it's > AMD/IOMMU: re-work mode updating [regression] > build: provide option to disambiguate symbol names [issue] > x86/vmx: always sync PIR to IRR before vmentry [issue]
Will ping Kevin now for feedback on the above. I think: x86/vlapic: allow setting APIC_SPIV_FOCUS_DISABLED in x2APIC mode [0] Should also be considered, since it's an issue. Thanks, Roger. [0] https://lists.xenproject.org/archives/html/xen-devel/2019-11/msg01153.html _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
