On Fri, May 03, 2024 at 06:54:40PM +0200, Oleksii wrote: > Hello everyone, > > I would like to share with you a list for status tracking based on Xen > ML and community members comments: > > *** Arm ***: > * Arm cache coloring [ > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > - new patch series version [v8] was sent > > * PCI devices passthrough on Arm, part 3 [ > https://lore.kernel.org/xen-devel/[email protected]/ > ] > > * DOMCTL-based guest magic region allocation for 11 > domUs [ > https://lore.kernel.org/xen-devel/[email protected]/ > ] > - new patch series verstion [v4] was sent > > * [XEN v6 0/3] xen/arm: Add emulation of Debug Data Transfer > Registers [ > https://patchew.org/Xen/[email protected]/ > ] > > *** PPC ***: > * [PATCH v4 0/6] Early Boot Allocation on Power [ > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > new patch series version [v4] was sent > > *** RISC-V ***: > * [PATCH v8 00/17] Enable build of full Xen for RISC-V > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > - several patches were merged > - new patch series version [v8] were sent > > > *** x86 ***: > * [PATCH 0/4] iommu/x86: fixes/improvements for unity range checks [ > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > - almost patch series have been merged already except the patch: > [PATCH 4/4] iommu/x86: make unity range checking more strict > > * [PATCH 0/8] x86: support AVX10.1 [ > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > - two patches of patch series are waitng to merged/reviewed: > [PATCH 1/4] amd-vi: fix IVMD memory type checks > [PATCH 4/4] iommu/x86: make unity range checking more strict > > * APX support? > > * [PATCH v4 0/8] x86emul: misc additions [ > https://lore.kernel.org/xen-devel/[email protected]/ > ] > > * [PATCH v2 00/12] VT-d: SATC handling; ATS: tidying[ > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > new version was sent [ v2 ] > > * [XEN PATCH 0/9] x86: parallelize AP bring-up during boot [ > https://lore.kernel.org/xen-devel/[email protected]/ > ] > > * [PATCH v2 00/12] x86: memcpy() / memset() (non-)ERMS flavors plus > fallout [ > https://lore.kernel.org/xen-devel/[email protected]/ > ] > - 6/12 are merged. > > * [PATCH v6 0/4] x86/pvh: Support relocating dom0 kernel [ > https://patchew.org/Xen/[email protected]/ > ]
Isn't this done? (at least the Xen side): dfc9fab00378 x86/PVH: Support relocatable dom0 kernels I have some minor stuff that was posted one day after feature freeze: xen/x86: support foreign mappings for HVM https://lore.kernel.org/xen-devel/[email protected]/ and tools/xen-cpuid: switch to use cpu-policy defined names https://lore.kernel.org/xen-devel/[email protected]/ Which I think would be nice to have for the release. The first one because it enables work on PVH-based QEMU stubdomains, the second it's a nice cleanup that makes it easier to introduce new CPUID features. Some series that I posted before the freeze: livepatch: minor bug fixes and improvements https://lore.kernel.org/xen-devel/[email protected]/ Patches 3 and 4 are pending review. xen: introduce Kconfig function alignment option https://lore.kernel.org/xen-devel/[email protected]/ Patch 2 is missing review. And then some patches that I don't expect to make progress: x86/shutdown: change default reboot method preference https://lore.kernel.org/xen-devel/[email protected]/ x86/time: prefer CMOS over EFI_GET_TIME https://lore.kernel.org/xen-devel/[email protected]/ I find it quite funny how everyone complains about all downstreams carrying similar patches to deal with firmware bugs, yet when I attempt to formally post them I get zero interest from such downstreams. Maybe raising them here will help get some eyes. Thanks, Roger.
