Currently the Intel reserved region is attached to the
RMRR unit and when building the list of RMRR seen by a device
we link this unique reserved region without taking care of
potential multiple usage of this reserved region by several devices.
Also while reading the vtd spec it is unclear to me whether
the RMRR device scope referenced by an RMRR ACPI struct could
be a PCI-PCI bridge, in which case I think we also need to
check the device belongs to the PCI sub-hierarchy of the device
referenced in the scope. This would be true for device_has_rmrr()
and intel_iommu_get_resv_regions().
Eric Auger (4):
iommu: Pass a GFP flag parameter to iommu_alloc_resv_region()
iommu/vt-d: Duplicate iommu_resv_region objects per device list
iommu/vt-d: Handle RMRR with PCI bridge device scopes
iommu/vt-d: Handle PCI bridge RMRR device scopes in
intel_iommu_get_resv_regions
drivers/acpi/arm64/iort.c | 3 +-
drivers/iommu/amd_iommu.c | 7 ++--
drivers/iommu/arm-smmu-v3.c | 2 +-
drivers/iommu/arm-smmu.c | 2 +-
drivers/iommu/intel-iommu.c | 68 +++++++++++++++++++++++--------------
drivers/iommu/iommu.c | 7 ++--
include/linux/iommu.h | 2 +-
7 files changed, 55 insertions(+), 36 deletions(-)
--
2.20.1
