This series attempts to make IOMMU device grouping a slightly more
integral part of the device model. iommu_device_groups were originally
introduced to support the VFIO user space driver interface which needs
to understand the granularity of device isolation in order to ensure
security of devices when assigned for user access. This information
was provided via a simple group identifier from the IOMMU driver allowing
VFIO to walk devices and assemble groups itself.
The feedback received from this was that groups should be the effective
unit of work for the IOMMU API. The existing model of allowing domains
to be created and individual devices attached ignores many of the
restrictions of the IOMMU, whether by design, by topology or by defective
devices. Additionally we should be able to use the grouping information
at the dma ops layer for managing domains and quirking devices.
This series is a sketch at implementing only those aspects and leaving
everything else about the multifaceted hairball of Isolation groups for
another API. Please comment and let me know if this seems like the
direction we should be headed. Thanks,
Alex
---
Alex Williamson (3):
iommu: Create attach/detach group interface
iommu: Create basic group infrastructure and update AMD-Vi & Intel VT-d
iommu: Introduce iommu_group
drivers/iommu/amd_iommu.c | 50 ++++++----
drivers/iommu/intel-iommu.c | 76 ++++++++--------
drivers/iommu/iommu.c | 210 ++++++++++++++++++++++++++++++++++++++-----
include/linux/device.h | 2
include/linux/iommu.h | 43 +++++++++
5 files changed, 301 insertions(+), 80 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
