summaryrefslogtreecommitdiffstats
path: root/usr.sbin
diff options
context:
space:
mode:
authormarius <marius@FreeBSD.org>2013-07-09 23:12:26 +0000
committermarius <marius@FreeBSD.org>2013-07-09 23:12:26 +0000
commit691f35718e7b841b431b170da764ea644755e29a (patch)
tree5da5dfc8ade1bd64946d0c34e8e5639953727710 /usr.sbin
parentb8b7a65ef6e19f27c3ddc091150988b207795128 (diff)
downloadFreeBSD-src-691f35718e7b841b431b170da764ea644755e29a.zip
FreeBSD-src-691f35718e7b841b431b170da764ea644755e29a.tar.gz
- As it turns out, not only MSI-X is broken for devices passed through by
VMware up to at least ESXi 5.1. Actually, using INTx in that case instead may still result in interrupt storms, with MSI being the only working option in some configurations. So introduce a PCI_QUIRK_DISABLE_MSIX quirk which only blacklists MSI-X but not also MSI and use it for the VMware PCI-PCI-bridges. Note that, currently, we still assume that if MSI doesn't work, MSI-X won't work either - but that's part of the internal logic and not guaranteed as part of the API contract. While at it, add and employ a pci_has_quirk() helper. Reported and tested by: Paul Bucher - Use NULL instead of 0 for pointers. Submitted by: jhb (mostly) Approved by: jhb MFC after: 3 days
Diffstat (limited to 'usr.sbin')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud