summaryrefslogtreecommitdiffstats
path: root/drivers/pcmcia/socket_sysfs.c
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2014-05-05 22:20:51 +0200
committerBjorn Helgaas <bhelgaas@google.com>2014-05-27 23:07:41 +0200
commit78916b00f0096059c872f537306b1a464c84fb30 (patch)
treef3ef41ae8a54215c83ce51db6f3573305a48eb72 /drivers/pcmcia/socket_sysfs.c
parentPCI: Remove pcibios_add_platform_entries() (diff)
downloadlinux-78916b00f0096059c872f537306b1a464c84fb30.tar.xz
linux-78916b00f0096059c872f537306b1a464c84fb30.zip
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 'drivers/pcmcia/socket_sysfs.c')
0 files changed, 0 insertions, 0 deletions