diff options
| author | Kuppuswamy Sathyanarayanan <[email protected]> | 2020-01-29 19:14:00 +0000 |
|---|---|---|
| committer | Bjorn Helgaas <[email protected]> | 2020-02-05 17:58:08 +0000 |
| commit | 2e34673be0bd6bb0c6c496a861cbc3f7431e7ce3 (patch) | |
| tree | 2396a39fd32329408f358366f05dfdd8c752fc61 /Documentation/filesystems/caching/netfs-api.rst | |
| parent | x86/PCI: Define to_pci_sysdata() even when !CONFIG_PCI (diff) | |
| download | kernel-2e34673be0bd6bb0c6c496a861cbc3f7431e7ce3.tar.gz kernel-2e34673be0bd6bb0c6c496a861cbc3f7431e7ce3.zip | |
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 <[email protected]>
Signed-off-by: Bjorn Helgaas <[email protected]>
CC: [email protected] # v5.5+
Diffstat (limited to 'Documentation/filesystems/caching/netfs-api.rst')
0 files changed, 0 insertions, 0 deletions