mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-01-30 06:01:28 +00:00
8873859ade
Instead of using the ACPI info template in the source tree, this patch requires a board-specific ACPI info header to be created by the user and placed under bsp/include. Currently we'll fall back to the current platform-specific template if such board-specific info is not available. A configuration symbol ACPI_ENFORCE_VALIDATED_ACPI_INFO is also added to enforce the existance of board-specific ACPI info header. Default configurations can set this symbol if the template does not work on a board. Updates to the getting started guide will be updated accordingly after the offline tools to generate such header is available. v2 -> v3: * Rephrase the ACPI-info-related messages. v1 -> v2: * The generated header should depend on .config so that whenever any configuration changes, this header will be remade. Tracked-On: #1520 Signed-off-by: Junjie Mao <junjie.mao@intel.com> Reviewed-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Anthony Xu <anthony.xu@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!