mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-07-15 19:05:32 +00:00
538ba08c2b
Now if the vmexit reason is virtulized EOI for level triggered interrupts, HV will loop all the ptdev entries, it is time-consuming, this patch add vpin to ptdev entry mapping for vpic and vioapic when add intx entry for a vm,it can use the ptdev entry directly according to the mapping for vpin and ptdev entry when EOI vmexit. v3-->v4: -- add check vpin in remove_intx_remapping -- move check vpin from ptdev_add_intx_remapping to add_intx_remapping Tracked-On: #861 Signed-off-by: Mingqiang Chi <mingqiang.chi@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com> Reviewed-by: Eddie Dong <eddie.dong@intel.com>
ACRN Hypervisor ############### The open source `Project ACRN`_ defines a device hypervisor reference stack and an architecture for running multiple software subsystems, managed securely, on a consolidated system by means of a virtual machine manager. It also defines a reference framework implementation for virtual device emulation, called the “ACRN Device Model”. The ACRN Hypervisor is a Type 1 reference hypervisor stack, running directly on the bare-metal hardware, and is suitable for a variety of IoT and embedded device solutions. The ACRN hypervisor addresses the gap that currently exists between datacenter hypervisors, and hard partitioning hypervisors. The ACRN hypervisor architecture partitions the system into different functional domains, with carefully selected guest OS sharing optimizations for IoT and embedded devices. You can find out more about Project ACRN on the `Project ACRN documentation`_ website. .. _`Project ACRN`: https://projectacrn.org .. _`ACRN Hypervisor`: https://github.com/projectacrn/acrn-hypervisor .. _`Project ACRN documentation`: https://projectacrn.github.io/