PCI: Never treat a VF as a multifunction device
authorAlex Williamson <alex.williamson@redhat.com>
Thu, 9 Jan 2014 15:36:08 +0000 (08:36 -0700)
committerBjorn Helgaas <bhelgaas@google.com>
Fri, 10 Jan 2014 17:05:26 +0000 (10:05 -0700)
commitaa9319773619c9d0caf2c4abc3ac12dc879dc8ed
treec8e0b767b863c83a470f5bbacf3a1c28561683f3
parentc2a5a829e28c476880b5efc8755ab3b339fdc147
PCI: Never treat a VF as a multifunction device

Per the SR-IOV spec rev 1.1:

  3.4.1.9 Header Type (Offset 0Eh)

  "... For VFs, this register must be RO Zero."

Unfortunately some devices get this wrong, ex. Emulex OneConnect 10Gb NIC.
When they do it makes us handle ACS testing and therefore IOMMU groups as
if they were actual multifunction devices and require ACS capabilities to
make sure there's no peer-to-peer between functions.  VFs are never
traditional multifunction devices, so simply clear this bit before we get
any further into setup.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=68431
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
drivers/pci/iov.c
This page took 0.024445 seconds and 5 git commands to generate.