acrn-hypervisor/hypervisor
Jason Chen CJ c244e8b5a3 vpic: use calloc to init vpic instead of malloc
vpic struct should be init as 0

Signed-off-by: Jason Chen CJ <jason.cj.chen@intel.com>
2018-05-15 17:19:36 +08:00
..
Documentation initial import 2018-05-11 14:44:28 +08:00
arch/x86 vpic: use calloc to init vpic instead of malloc 2018-05-15 17:19:36 +08:00
boot initial import 2018-05-11 14:44:28 +08:00
bsp minor fix on acrn.conf 2018-05-11 14:44:30 +08:00
common apicv: cancel event injection if vcpu is scheduled out 2018-05-15 17:19:36 +08:00
debug initial import 2018-05-11 14:44:28 +08:00
include apicv: cancel event injection if vcpu is scheduled out 2018-05-15 17:19:36 +08:00
lib initial import 2018-05-11 14:44:28 +08:00
MAINTAINERS update Maintainer list 2018-05-11 14:44:28 +08:00
Makefile security: fortify source and format string check 2018-05-15 17:19:35 +08:00
README.rst initial import 2018-05-11 14:44:28 +08:00
license_header initial import 2018-05-11 14:44:28 +08:00

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!