mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-01-04 23:24:56 +00:00
To reduce the call to dynamic memory allocation, the patch tries to alloate memroy together with hypervisor when hypervisor is being relocated by efi stub code. The memory allocated will be right at the end of HV memory. Three structs will be done in this way: 1) boot_ctx, which saves EFI boot state and is passed to SOS; 2) multiboot_info, faked multi-boot header for passing boot info to hypervisor; and 3) multiboot_mmap, e820 mmap structure. after this, the EFI stub code (which boot hypervisor) will only have 3 to dynamic memory: 1. the call for hv binary and the 3 struct; 2. the call to CPU boot trampoline code; 3. the call to alloc mmap buf when inquery memory layout from UEFI FW; Tracked-On:#1260 Signed-off-by: Chaohong Guo <chaohong.guo@intel.com> Reviewed-by: Jason Chen <jason.cj.chen@intel.com> Reviewed-by: Anthony Xu <Anthony.Xu@intel.com> Reviewed-by: Eddie Dong <Eddid.Dong@intel.com> Acked-by: Gen Zheng <gen.zheng@intel.com>
Embedded-Hypervisor ################### This open source embedded hypervisor defines a software architecture for running multiple software subsystems managed securely on a consolidated system (by means of a virtual machine manager), and defines a reference framework Device Model implementation for devices emulation This embedded hypervisor is type-1 reference hypervisor, running directly on the system hardware. It can be used for building software defined cockpit (SDC) or In-Vehicle Experience (IVE) solutions running on Intel Architecture Apollo Lake platforms. As a reference implementation, it provides the basis for embedded hypervisor vendors to build solutions with an open source reference I/O mediation solution, and provides auto makers a reference software stack for SDC usage. This embedded hypervisor is able to support both Linux* and Android* as a Guest OS, managed by the hypervisor, where applications can run. This embedded hypervisor is a partitioning hypervisor reference stack, also suitable for non-automotive IoT & embedded device solutions. It will be addressing the gap that currently exists between datacenter hypervisors, hard partitioning hypervisors, and select industrial applications. Extending the scope of this open source embedded hypervisor relies on the involvement of community developers like you!