Li Fei1 e5c7a96513 hv: vpci: sos could access low severity guest pci cfg space ... There're some cases the SOS (higher severity guest) needs to access the post-launched VM (lower severity guest) PCI CFG space: 1. The SR-IOV PF needs to reset the VF 2. Some pass through device still need DM to handle some quirk. In the case a device is assigned to a UOS and is not in a zombie state, the SOS is able to access, if and only if the SOS has higher severity than the UOS. Tracked-On: #4371 Signed-off-by: Li Fei1 <fei1.li@intel.com>		2020-03-20 10:08:43 +08:00
..
pci_pt.c	hv: unmap SR-IOV VF MMIO when the VF physical device is disabled	2020-03-18 21:46:54 +08:00
vdev.c	hv: refine naming	2020-03-11 08:35:30 +08:00
vhostbridge.c	hv: vpci: add _v prefix for some function name	2020-03-09 17:09:55 +08:00
vmsi.c	hv: refine read/write configuration APIs for vmsi/vmsix	2020-03-12 10:40:02 +08:00
vmsix.c	hv: refine read/write configuration APIs for vmsi/vmsix	2020-03-12 10:40:02 +08:00
vpci_bridge.c	hv: vpci: add _v prefix for some function name	2020-03-09 17:09:55 +08:00
vpci_priv.h	hv: unmap SR-IOV VF MMIO when the VF physical device is disabled	2020-03-18 21:46:54 +08:00
vpci.c	hv: vpci: sos could access low severity guest pci cfg space	2020-03-20 10:08:43 +08:00
vsriov.c	hv: unmap SR-IOV VF MMIO when the VF physical device is disabled	2020-03-18 21:46:54 +08:00