diff options
author | Alex Williamson <alex.williamson@redhat.com> | 2014-05-05 14:20:51 -0600 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2014-05-27 15:07:41 -0600 |
commit | 78916b00f0096059c872f537306b1a464c84fb30 (patch) | |
tree | f3ef41ae8a54215c83ce51db6f3573305a48eb72 /arch/unicore32 | |
parent | 9edbcd2252b5ef148177c9f2c11a56469cf5db52 (diff) | |
download | op-kernel-dev-78916b00f0096059c872f537306b1a464c84fb30.zip op-kernel-dev-78916b00f0096059c872f537306b1a464c84fb30.tar.gz |
PCI: Test for std config alias when testing extended config space
When a PCI-to-PCIe bridge is stacked on a PCIe-to-PCI bridge, we can have
PCIe endpoints masked by a conventional PCI bus. This makes the extended
config space of the PCIe endpoint inaccessible. The PCIe-to-PCI bridge is
supposed to handle any type 1 configuration transactions where the extended
config offset bits are non-zero as an Unsupported Request rather than
forward it to the secondary interface. As noted here, there are a couple
known offenders to this rule. These bridges drop the extended offset bits,
resulting in the conventional config space being aliased many times across
the extended config space. For Intel NICs, this alias often seems to
expose a bogus SR-IOV cap.
Stacking bridges may seem like an uncommon scenario, but note that any
conventional PCI slot in a modern PC is already the secondary interface of
an onboard PCIe-to-PCI bridge. The user need only add a PCI-to-PCIe
adapter and PCIe device to encounter this problem.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'arch/unicore32')
0 files changed, 0 insertions, 0 deletions