vfio-pci: Enable raw access to unassigned config space
authorAlex Williamson <alex.williamson@redhat.com>
Mon, 1 Apr 2013 15:04:12 +0000 (09:04 -0600)
committerAlex Williamson <alex.williamson@redhat.com>
Mon, 1 Apr 2013 15:04:12 +0000 (09:04 -0600)
commita7d1ea1c11b33bda2691f3294b4d735ed635535a
treef1fc761f89fb0f60b9b89c3e5f18c888758ce344
parent180b1381078924b2442a42cded514afd6faff458
vfio-pci: Enable raw access to unassigned config space

Devices like be2net hide registers between the gaps in capabilities
and architected regions of PCI config space.  Our choices to support
such devices is to either build an ever growing and unmanageable white
list or rely on hardware isolation to protect us.  These registers are
really no different than MMIO or I/O port space registers, which we
don't attempt to regulate, so treat PCI config space in the same way.

Reported-by: Gavin Shan <shangw@linux.vnet.ibm.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Tested-by: Gavin Shan <shangw@linux.vnet.ibm.com>
drivers/vfio/pci/vfio_pci_config.c