summary refs log tree commit diff stats
path: root/include/hw/intc
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2018-02-06 11:08:27 -0700
committerAlex Williamson <alex.williamson@redhat.com>2018-02-06 11:08:27 -0700
commitdb32d0f43839627f54a1a7f8eee17baa770f52d2 (patch)
tree6087f8376856af72ef6503f2dc6787856e23eb55 /include/hw/intc
parenta5b04f7c5380340342ad5623b34c57fe3bab9b29 (diff)
downloadfocaccia-qemu-db32d0f43839627f54a1a7f8eee17baa770f52d2.tar.gz
focaccia-qemu-db32d0f43839627f54a1a7f8eee17baa770f52d2.zip
vfio/pci: Add option to disable GeForce quirks
These quirks are necessary for GeForce, but not for Quadro/GRID/Tesla
assignment.  Leaving them enabled is fully functional and provides the
most compatibility, but due to the unique NVIDIA MSI ACK behavior[1],
it also introduces latency in re-triggering the MSI interrupt.  This
overhead is typically negligible, but has been shown to adversely
affect some (very) high interrupt rate applications.  This adds the
vfio-pci device option "x-no-geforce-quirks=" which can be set to
"on" to disable this additional overhead.

A follow-on optimization for GeForce might be to make use of an
ioeventfd to allow KVM to trigger an irqfd in the kernel vfio-pci
driver, avoiding the bounce through userspace to handle this device
write.

[1] Background: the NVIDIA driver has been observed to issue a write
to the MMIO mirror of PCI config space in BAR0 in order to allow the
MSI interrupt for the device to retrigger.  Older reports indicated a
write of 0xff to the (read-only) MSI capability ID register, while
more recently a write of 0x0 is observed at config space offset 0x704,
non-architected, extended config space of the device (BAR0 offset
0x88704).  Virtualization of this range is only required for GeForce.

Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'include/hw/intc')
0 files changed, 0 insertions, 0 deletions