mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-06-27 15:56:54 +00:00
Project ACRN hypervisor
As mentioned in https://github.com/projectacrn/acrn-documentation/pull/38 on some operating systems, the ``gnu-efi`` package installs the linker under a ``gnuefi`` folder in ``${LIBDIR}``. This is the case in Fedora for example. Check if the gnuefi folder is there and use it if it is in the path to the linker. This PR fixes the Makefile rather than documenting how to edit it yourself. Signed-off-by: David B. Kinder <david.b.kinder@intel.com> |
||
---|---|---|
arch/x86 | ||
boot | ||
bsp | ||
common | ||
debug | ||
Documentation | ||
include | ||
lib | ||
.gitignore | ||
license_header | ||
MAINTAINERS | ||
Makefile | ||
README.rst |
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!