Alex Williamson 81fb345971 vfio/pci: Fix SR-IOV VF handling with MMIO blocking ... commit ebfa440ce3 upstream. SR-IOV VFs do not implement the memory enable bit of the command register, therefore this bit is not set in config space after pci_enable_device(). This leads to an unintended difference between PF and VF in hand-off state to the user. We can correct this by setting the initial value of the memory enable bit in our virtualized config space. There's really no need however to ever fault a user on a VF though as this would only indicate an error in the user's management of the enable bit, versus a PF where the same access could trigger hardware faults. Fixes: abafbc551f ("vfio-pci: Invalidate mmaps and block MMIO access on disabled memory") Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2020-09-09 19:04:32 +02:00
..
mdev	vfio/mdev: Fix reference count leak in add_mdev_supported_type	2020-06-25 15:33:01 +02:00
pci	vfio/pci: Fix SR-IOV VF handling with MMIO blocking	2020-09-09 19:04:32 +02:00
platform	vfio: platform: Fix using devices in PM Domains	2018-06-08 10:24:37 -06:00
Kconfig
Makefile
vfio_iommu_spapr_tce.c	vfio/spapr_tce: Get rid of possible infinite loop	2019-12-05 09:20:43 +01:00
vfio_iommu_type1.c	vfio/type1: Support faulting PFNMAP vmas	2020-09-09 19:04:28 +02:00
vfio_spapr_eeh.c
vfio.c	vfio: Fix WARNING "do not call blocking ops when !TASK_RUNNING"	2019-06-15 11:54:07 +02:00
virqfd.c