summaryrefslogtreecommitdiffstats
path: root/include/linux/intel-iommu.h
diff options
context:
space:
mode:
authorAshok Raj <ashok.raj@intel.com>2016-10-21 15:32:05 -0700
committerDavid Woodhouse <dwmw2@infradead.org>2016-10-30 05:32:51 -0600
commit1c387188c60f53b338c20eee32db055dfe022a9b (patch)
tree1d97936df0da7e4584e35c6e2de9cac48eb1e0b8 /include/linux/intel-iommu.h
parenta909d3e636995ba7c349e2ca5dbb528154d4ac30 (diff)
downloadlinux-1c387188c60f53b338c20eee32db055dfe022a9b.tar.gz
linux-1c387188c60f53b338c20eee32db055dfe022a9b.tar.xz
iommu/vt-d: Fix IOMMU lookup for SR-IOV Virtual Functions
The VT-d specification (§8.3.3) says: ‘Virtual Functions’ of a ‘Physical Function’ are under the scope of the same remapping unit as the ‘Physical Function’. The BIOS is not required to list all the possible VFs in the scope tables, and arguably *shouldn't* make any attempt to do so, since there could be a huge number of them. This has been broken basically for ever — the VF is never going to match against a specific unit's scope, so it ends up being assigned to the INCLUDE_ALL IOMMU. Which was always actually correct by coincidence, but now we're looking at Root-Complex integrated devices with SR-IOV support it's going to start being wrong. Fix it to simply use pci_physfn() before doing the lookup for PCI devices. Cc: stable@vger.kernel.org Signed-off-by: Sainath Grandhi <sainath.grandhi@intel.com> Signed-off-by: Ashok Raj <ashok.raj@intel.com> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'include/linux/intel-iommu.h')
0 files changed, 0 insertions, 0 deletions