Hi Alex,
Here are the parts of my recent series to allow VFIO devices on the
spapr-pci-host-bridge device which affect the core VFIO code. They've
been revised according to the comments from yourself and others.
There's also one patch for the memory subsystem.
Note that while these are motivated by the needs of the sPAPR code,
they changes should all be generally correct, and will allow safer and
more flexible use of VFIO devices in other potential situations as
well.
Please apply.
Changes since v2:
* Reworked IOMMU notifier replay mechanism according to Paolo's
suggestions.
Changes since v1:
* Assorted minor cleanups based on comments.
*** BLURB HERE ***
David Gibson (7):
vfio: Remove unneeded union from VFIOContainer
vfio: Generalize vfio_listener_region_add failure path
vfio: Check guest IOVA ranges against host IOMMU capabilities
vfio: Record host IOMMU's available IO page sizes
memory: Allow replay of IOMMU mapping notifications
vfio: Allow hotplug of containers onto existing guest IOMMU mappings
vfio: Expose a VFIO PCI device's group for EEH
hw/vfio/common.c | 140 ++++++++++++++++++++++++++----------------
hw/vfio/pci.c | 14 +++++
include/exec/memory.h | 13 ++++
include/hw/vfio/vfio-common.h | 23 +++----
include/hw/vfio/vfio-pci.h | 11 ++++
memory.c | 20 ++++++
6 files changed, 154 insertions(+), 67 deletions(-)
create mode 100644 include/hw/vfio/vfio-pci.h
--
2.4.3
