mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-01-13 19:44:06 +00:00
64ecf193e4
PCI ROM is the firmware specific to PCI device and it is provided by the device vendor. The PCI rom resides in 0x30 offset of PCI config space. This can be used to check whether the PCI rom exists. And when it exists, it can load the firmware from the addr that is obtained from ROM bar addr. For the user-vm, it will try to load the rom_file for the given PCI device and enable the VM to access the firmware that is defined in rom_file. BTW: The emulated rom_file is converted from efi image by using EfiRom. It has no dependency on the ROM bar of physical PCI devices. Of course if the physical PCI devices supports the ROM bar, the rom_file can also be dumped from the PCI rom. Now this is limited to PCI display device. V2->V3: Add the function of pci_load_rombar/pci_release_rombar to handle the rombar in course of passthrough_init/deinit. Tracked-On: #8175 Signed-off-by: Zhao Yakui <yakui.zhao@intel.com> Acked-by: Wang Yu <yu1.wang@intel.com>
ACRN Device Model ################# Introduction ============ The ACRN Device Model provides **device sharing** capabilities between the Service VM and post-launched User VMs. It is a component that is used in conjunction with the `ACRN Hypervisor`_ and is installed within the Service VM. .. _`ACRN Hypervisor`: https://github.com/projectacrn/acrn-hypervisor