| commit | edfbb1affe9454a32cb55c0c77dedac0b60746f5 | |
| author | David Woodhouse <dwmw2@infradead.org> | |
| Tue, 5 May 2009 08:25:23 +0000 (5 09:25 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 8 May 2009 22:45:10 +0000 (8 15:45 -0700) | ||
| tree | 6d6fa28f1677ce75733d12937361dd36a9ec2391 | treesnapshot (tar.gz zip) |
| parent | 80c2d4701095c98d01ae4cda681bd231625e4ac7 | commitdiff |
intel-iommu: Fix device-to-iommu mapping for PCI-PCI bridges.
(cherry picked from commit 924b6231edfaf1e764ffb4f97ea382bf4facff58)
When the DMAR table identifies that a PCI-PCI bridge belongs to a given
IOMMU, that means that the bridge and all devices behind it should be
associated with the IOMMU. Not just the bridge itself.
This fixes the device_to_iommu() function accordingly.
(It's broken if you have the same PCI bus numbers in multiple domains,
but this function was always broken in that way; I'll be dealing with
that later).
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
(cherry picked from commit 924b6231edfaf1e764ffb4f97ea382bf4facff58)
When the DMAR table identifies that a PCI-PCI bridge belongs to a given
IOMMU, that means that the bridge and all devices behind it should be
associated with the IOMMU. Not just the bridge itself.
This fixes the device_to_iommu() function accordingly.
(It's broken if you have the same PCI bus numbers in multiple domains,
but this function was always broken in that way; I'll be dealing with
that later).
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/pci/intel-iommu.c | diffblobblamehistory |