mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-06 23:46:58 +00:00
041a7dec98
In current design, when pass-thru dev, for the PIO bar, need to ensure the guest PIO start address equals to host PIO start address. Then set the VMCS io bitmap to pass-thru the corresponding port io to guest for performance. But malicious guest may reprogram the PIO bar, then hv will pass-thru the reprogramed PIO address to guest. This isn't safe behavior. Here only pass-thru the host physical device PIO to guest. If guest regrogram the PIO bar, just update the virtual bar only. Currently, we don't support PIO bar reprogramming, if guest reprogram the PIO bar, guest should take responsibility itself When init the pass-thru dev PIO bars, set the VMCS io bitmap. setup_io_bitmap is called before init pass-thru dev to initiailize the io bitmap, so don't need to call deny_guest_pio_access when deinit pass-thru dev. v1 -> v2: * set the VMCS io bitmap when init pass-thru devices to migrate redoing allow_guest_pio_access()/deny_guest_pio_access(). Tracked-On: #6508 Signed-off-by: Liu,Junming <junming.liu@intel.com> |
||
|---|---|---|
| .. | ||
| ivshmem.c | ||
| pci_pt.c | ||
| vdev.c | ||
| vhostbridge.c | ||
| vmcs9900.c | ||
| vmsi.c | ||
| vmsix_on_msi.c | ||
| vmsix.c | ||
| vpci_bridge.c | ||
| vpci_priv.h | ||
| vpci.c | ||
| vroot_port.c | ||
| vsriov.c | ||