feat(xen): pv-iommu integration patches

config.yaml

@@ -128,6 +128,41 @@ patches:
   - hyperv/0005-x86-hyperv-take-vPCI-device-interrupts-through-Xen-w.patch
   - hyperv/0006-drivers-hv-refuse-to-balloon-when-nested-on-Xen.patch
   series: '6.18'
+# Xen PV-IOMMU: let a PV guest program IOMMU contexts through the PV-IOMMU
+# hypercall interface, so passed-through devices DMA through a real translation
+# context instead of relying on an identity map. Includes the parallel
+# io-pgtable used for iova_to_phys, the pcifront machine-BDF lookup the
+# hypercalls need, and the PV MSI/MSI-X fixes that go with it.
+#
+# Pinned to the 6.18 series, not `lower`. iommu_domain_ops::attach_dev gained a
+# third `struct iommu_domain *old` argument in 6.19, so this backport only
+# compiles against 6.18.x. It is not enough to let the range run open-ended:
+# `patch -p1` still applies these to 6.19 with fuzz and the build then fails on
+# the incompatible function pointer, so the upper bound has to be explicit. A
+# forward-port for 6.19+ wants the three-argument attach_dev and belongs in a
+# separate patches/pv-iommu/ directory alongside this one.
+#
+# These files are trimmed relative to the edera/azenla/feat/pv-iommu branch they
+# come from: commit 1 there also carries stray hunks belonging to two other
+# series -- the VIRQ_HYPERV_* defines in include/xen/interface/xen.h and the
+# XENMEM_get_mfn_pxms block in include/xen/interface/memory.h -- which this tree
+# already supplies from patches/hyperv/ and
+# 0002-xen-add-xen_mfn_to_node-to-resolve-a-foreign-frame-s.patch. Both are
+# dropped here. If you regenerate these patches from that branch, drop them
+# again or the 6.18 stack collides on those two headers.
+- patches:
+  - pv-iommu-6.18/0001-iommu-xen-Add-Xen-PV-IOMMU-driver.patch
+  - pv-iommu-6.18/0002-iommu-xen-Allow-the-PV-IOMMU-driver-in-a-guest.patch
+  - pv-iommu-6.18/0003-iommu-xen-Give-the-identity-domain-a-type-and-ops.patch
+  - pv-iommu-6.18/0004-iommu-dma-Don-t-reserve-PCI-windows-under-a-paravirt.patch
+  - pv-iommu-6.18/0005-xen-pcifront-Let-callers-ask-for-a-device-s-machine-.patch
+  - pv-iommu-6.18/0006-iommu-xen-Default-a-PV-guest-to-the-identity-context.patch
+  - pv-iommu-6.18/0007-PCI-MSI-don-t-write-the-MSI-X-table-in-a-Xen-PV-gues.patch
+  - pv-iommu-6.18/0008-iommu-xen-batch-map-subops-over-contiguous-runs.patch
+  - pv-iommu-6.18/0009-iommu-xen-do-not-claim-the-IOMMU-itself.patch
+  - pv-iommu-6.18/0010-x86-xen-disable-the-right-interrupt-type-when-tearin.patch
+  - pv-iommu-6.18/0011-iommu-xen-flush-the-IOTLB-once-per-mapping-not-once-.patch
+  series: '6.18'
 - patch: 0001-feat-xen-deflate-balloon-via-oom-notifier.patch
   lower: '6.18'
 # virtio-gpu decides between DMA and guest-physical addresses on its own,

configs/x86_64/host.config

@@ -4859,6 +4859,7 @@ CONFIG_INTEL_IOMMU_FLOPPY_WA=y
 CONFIG_INTEL_IOMMU_PERF_EVENTS=y
 CONFIG_IRQ_REMAP=y
 CONFIG_HYPERV_IOMMU=y
+CONFIG_XEN_IOMMU=y
 
 
 CONFIG_RPMSG=m

configs/x86_64/zone.config

@@ -1032,6 +1032,7 @@ CONFIG_INTEL_IOMMU_DEFAULT_ON=y
 CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y
 CONFIG_INTEL_IOMMU_PERF_EVENTS=y
 CONFIG_IRQ_REMAP=y
+CONFIG_XEN_IOMMU=y
 
 CONFIG_MEMORY=y