On 03.05.2024 18:54, Oleksii wrote: > *** 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
This sub-item doesn't really fit the topic, and seems to rather belong to the earlier one? Where (correctly) 1/4 isn't listed anymore, for having gone in. As to 4/4 - Roger, I'm not sure I can conclude what the plan here was: Are you meaning to submit an updated version, or did we rather settle on not further pursuing this? > * APX support? I think you should drop this now. I'm throttling further work on the insn emulator, as long as I have so many other patches there pending review. > * [PATCH v6 0/4] x86/pvh: Support relocating dom0 kernel [ > https://patchew.org/Xen/[email protected]/ > ] There had been a v7, and all of that plus a follow-on adjustment have gone in. > *** common ***: > * annotate entry points with type and size" series: > The bulk of this has gone in, but there'll want to be follow-ups. I think these follow-ups now want tracking on a per-arch basis (x86 and Arm, with PPC and RISC-V filly done). > * [PATCH v2 (resend) 00/27] Remove the directmap [ > https://lore.kernel.org/xen-devel/[email protected]/ > ] > - 7/27 were merged. Hmm, no, I don't think that one was. Other were, yes. > * [PATCH v6 0/7] MSI-X support with qemu in stubdomain, and other > related changes: > - new patch version was sent 1/7 was committed. > * [PATCH v3 0/4] xenwatchdogd bugfixes and enhancements [ > https://lore.kernel.org/xen-devel/[email protected]/ > ]: > new patch series were sent. Was there anything left from that series? Jan
