mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-31 03:15:42 +00:00
There are some massages which is not fatal error but should to print to serial and sbuf(hvlog) at the same time. pr_fatal is for fatal error massages and it is not good choice for the situation above. Introduce a new API pr_acrnlog to deal with the situation. And replace the following printf with pr_acrnlog for massages should be print to sbuf and serial. Then developers can get those massages on serial and BTM(Boot Time Measurement) can use acrnlog to get those massages from sbuf. BTM refers to Boot Time Measurement which will read acrnlog file to get timestamps of steps we want. Signed-off-by: Kaige Fu <kaige.fu@intel.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> |
||
---|---|---|
.. | ||
.travis-dockerfiles | ||
arch/x86 | ||
boot | ||
bsp | ||
common | ||
debug | ||
Documentation | ||
include | ||
lib | ||
.travis.yml | ||
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!