[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Xen 4.20 Development Update [November]
On 12/4/24 12:01 PM, Jan Beulich wrote:
On 04.12.2024 11:20, Oleksii Kurochko wrote:=== x86 === * Expose consistent topology to guests (v7) - Alejandro Vallejo - https://lore.kernel.org/xen-devel/20241021154600.11745-1-alejandro.vallejo@xxxxxxxxx/T/#m6033f95c660675039d7789d3af1ba2f292a3a69b * Boot modules for Hyperlaunch (v8 -> v9) - Daniel P. Smith - https://patchew.org/Xen/20241115131204.32135-1-dpsmith@xxxxxxxxxxxxxxxxxxxx/ * x86/mm: miscellaneous fixes (v2 -> v3) - Roger Pau Monne - https://patchew.org/Xen/20241114145715.59777-1-roger.pau@xxxxxxxxxx/This went in, didn't it? Yes, you are right. It is fully in staging now.
* Address Space Isolation FPU preparations (v2) - Alejandro Vallejo - https://lore.kernel.org/xen-devel/20241105143310.28301-1-alejandro.vallejo@xxxxxxxxx/T/#mbca5192d7e5636ef5ea005a083e5ff28ebe6317d * x86/alternatives: Adjust all insn-relative fields (v2) - Andrew Cooper - https://lore.kernel.org/xen-devel/20241002152725.1841575-1-andrew.cooper3@xxxxxxxxxx/T/#mac2deaea7e02a343210d61887486433d946ad129 * Support device passthrough when dom0 is PVH on Xen (v16) - Jiqian Chen - https://lore.kernel.org/xen-devel/20240930034250.2682265-1-Jiqian.Chen@xxxxxxx/T/#m5d557d76f290ff5b5550c1443cab5774d397e526Some of this went in too, I think? "Support device passthrough when dom0 is PVH on Xen" should be moved to Completed. ( Accidentally did a grep for the cover letter subject not for the subject of the 1st patch so though that 1st patch isn't merged. And it seems to me that it should be mentioned in CHANGELOG.md, shouldn't it? * x86emul: misc additions (v5 -> v7) - Jan Beulich - https://patchew.org/Xen/3a25cd59-e1cb-4bfc-b868-fb11599d22f5@xxxxxxxx/ * x86/HVM: emulation (MMIO) improvements (v2) - Jan Beulich - https://lore.kernel.org/xen-devel/3294f629-f91f-4b5d-9eb0-40a34aa2ec3e@xxxxxxxx/ * x86: support AVX10.1 (v2) - Jan Beulich - https://lore.kernel.org/xen-devel/bcfea345-57c1-43d9-82b3-240b685486cc@xxxxxxxx/In v2 the title had changed to "x86: support AVX10", dealing with a first aspect of AVX10.2 as well. I have long completed AVX10.2 work, yet there was little reason to re-post without having got any feedback. Thanks, I will update the subject.
* APX support (v?) - Jan Beulich - ?I think you want to remove this from the list. While I have completed work there, I'm not fancying re-basing ahead of the AVX10 work, and hence that needs to go in first anyway. Which seems unlikely enough at this point, for 4.20.* VT-d: SATC handling; ATS: tidying (v2) - Jan Beulich - https://patchew.org/Xen/64b028be-2197-4951-ae5b-32f9eabfa84a@xxxxxxxx/ * x86: parallelize AP bring-up during boot (v1) - Krystian Hebel - https://lore.kernel.org/xen-devel/cover.1699982111.git.krystian.hebel@xxxxxxxxx/ * x86: memcpy() / memset() (non-)ERMS flavors plus (v3) - Jan Beulich - https://lore.kernel.org/xen-devel/e7314ac8-ed09-4da8-b915-09409b01fe77@xxxxxxxx/Isn't this the same as ...* x86/spec-ctrl: IBPB improvements (v4) - Jan Beulich - https://patchew.org/Xen/06591b64-2f05-a4cc-a2f3-a74c3c4a76d6@xxxxxxxx/ * Move some boot code from assembly to C (v2) - Frediano Ziglio - https://patchew.org/Xen/20241122093358.478774-1-frediano.ziglio@xxxxxxxxx/ * Hyperlaunch device tree for dom0 (v1) - Daniel P. Smith - https://patchew.org/Xen/20241123182044.30687-1-dpsmith@xxxxxxxxxxxxxxxxxxxx/ * x86: memcpy() / memset() (non-)ERMS flavors plus fallout (v3) - Jan Beulich - https://patchew.org/Xen/e7314ac8-ed09-4da8-b915-09409b01fe77@xxxxxxxx/... this? This is the same and one of them I will drop for the next report.
* amd-pstate CPU Performance Scaling Driver (v1) - Penny Zheng - https://patchew.org/Xen/20241203081111.463400-1-Penny.Zheng@xxxxxxx/This series was posted only this week, and upon asking it was clarified that it's indeed not aiming at 4.20. Yes, it is definitely not for the current one release. Probably it would make sense to add the extra line information that it is for the next one release. ~ Oleksii
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |