diff options
author | Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com> | 2020-01-29 22:14:00 +0300 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2020-02-05 20:58:08 +0300 |
commit | 2e34673be0bd6bb0c6c496a861cbc3f7431e7ce3 (patch) | |
tree | 2396a39fd32329408f358366f05dfdd8c752fc61 /arch | |
parent | b9303bb1990950bd2f49ec1c85c015b5b6aac24b (diff) | |
download | linux-2e34673be0bd6bb0c6c496a861cbc3f7431e7ce3.tar.xz |
PCI/ATS: Use PF PASID for VFs
Per PCIe r5.0, sec 9.3.7.14, if a PF implements the PASID Capability, the
PF PASID configuration is shared by its VFs, and VFs must not implement
their own PASID Capability. But commit 751035b8dc06 ("PCI/ATS: Cache PASID
Capability offset") changed pci_max_pasids() and pci_pasid_features() to
use the PASID Capability of the VF device instead of the associated PF
device. This leads to IOMMU bind failures when pci_max_pasids() and
pci_pasid_features() are called for VFs.
In pci_max_pasids() and pci_pasid_features(), always use the PF PASID
Capability.
Fixes: 751035b8dc06 ("PCI/ATS: Cache PASID Capability offset")
Link: https://lore.kernel.org/r/fe891f9755cb18349389609e7fed9940fc5b081a.1580325170.git.sathyanarayanan.kuppuswamy@linux.intel.com
Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
CC: stable@vger.kernel.org # v5.5+
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions