summaryrefslogtreecommitdiffstats
path: root/drivers/powercap
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2018-09-25 21:01:27 +0200
committerAlex Williamson <alex.williamson@redhat.com>2018-09-25 21:01:27 +0200
commitdb04264fe9bc0f2b62e036629f9afb530324b693 (patch)
tree6b80e98b183c9c3c36ff2ae3dcf2c41e906766e1 /drivers/powercap
parentvfio/pci: Fix potential memory leak in vfio_msi_cap_len (diff)
downloadlinux-db04264fe9bc0f2b62e036629f9afb530324b693.tar.xz
linux-db04264fe9bc0f2b62e036629f9afb530324b693.zip
vfio/pci: Mask buggy SR-IOV VF INTx support
The SR-IOV spec requires that VFs must report zero for the INTx pin register as VFs are precluded from INTx support. It's much easier for the host kernel to understand whether a device is a VF and therefore whether a non-zero pin register value is bogus than it is to do the same in userspace. Override the INTx count for such devices and virtualize the pin register to provide a consistent view of the device to the user. As this is clearly a spec violation, warn about it to support hardware validation, but also provide a known whitelist as it doesn't do much good to continue complaining if the hardware vendor doesn't plan to fix it. Known devices with this issue: 8086:270c Tested-by: Gage Eads <gage.eads@intel.com> Reviewed-by: Ashok Raj <ashok.raj@intel.com> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'drivers/powercap')
0 files changed, 0 insertions, 0 deletions