@@ -2018,7 +2018,7 @@ static struct dmar_domain *get_domain_for_dev(struct pci_dev *pdev, int gaw)
struct dmar_domain *domain;
struct intel_iommu *iommu;
struct dmar_drhd_unit *drhd;
- struct pci_dev *bridge;
+ struct pci_dev *bridge, *parent;
unsigned long flags;
int segment, bus, devfn;
@@ -2072,6 +2072,13 @@ static struct dmar_domain *get_domain_for_dev(struct pci_dev *pdev, int gaw)
domain_exit(domain);
goto error;
}
+ /* also register intermediate P2P bridges */
+ for (parent = pdev->bus->self; parent != bridge;
+ parent = parent->bus->self) {
+ if (dmar_insert_dev_info(segment, parent->bus->number,
+ parent->devfn, NULL, &domain))
+ goto error;
+ }
}
found_domain:
When creating DMAR domain for a PCI device, we will only associate the PCI device and upstream (PCIe) bridge with the domain and skip all intermediate P2P bridges. Function domain_context_mapping() will attach the created domain to the PCI device, the upstream (PCIe) bridge and all intermediate P2P bridge. Later when domain_remove_dev_info() is called, it only detaches the domain from the PCI device and its upstream (PCIe) bridge and leaves the domain still attached to all intermediate P2P bridges. This stale state may cause troubles when we assign the affected PCI hierarchy to a virtual machine later. So also create device_domain_info for intermediate P2P bridges when creating domain for PCI device. Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com> Cc: Alex Williamson <alex.williamson@redhat.com> --- drivers/iommu/intel-iommu.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)