mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-12-01 04:33:58 +00:00
01fa6de42c
Sometimes the memory to be allocated is not at the end of an entry, that means we have to break one enty into 2 smaller entries, there are two ways to add the new entry to hv_e820, adds to the end or insert it. The initial e820 table is ordered, that's why the e820_alloc_memory interface asssum all entries was sorted, but add new entry to the end will break the orde of hv_e820. So we use insert_e820_entry to replace the add_e820_entry, the new interfeac will keep the orde and users do not need sort again after alloc region Tracked-On: #6690 Acked-by: Anthony Xu <anthony.xu@intel.com> Signed-off-by: Chenli Wei<chenli.wei@linux.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/