acrn-hypervisor

History

Victor Sun 04d82e5c0f HV: return virtual lapic id in vcpuid 0b leaf Currently vlapic id of SOS VM is virtualized, it is indexed by vcpuid in physical APIC id sequence, but CPUID 0BH leaf still report physical APIC ID. In SDC/INDUSTRY scenario they are identical mapping so no issue occured. In hybrid mode this would be a problem because vAPIC ID might be different with pAPIC ID. We need to make the APIC ID which returned from CPUID consistent with the one returned from LAPIC register. Tracked-On: #3214 Signed-off-by: Victor Sun <victor.sun@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>		2019-06-06 15:22:10 +08:00
..
acpi_parser	hv: use 64bit FACS table address only beyond ACPI2.0	2019-05-30 16:47:19 +08:00
arch/x86	HV: return virtual lapic id in vcpuid 0b leaf	2019-06-06 15:22:10 +08:00
boot	HV: misra fix for patch set of Zephyr enabling	2019-06-06 09:40:52 +08:00
bsp/ld	hv: dmar_parse: remove dynamic memory allocation	2019-05-10 11:33:37 +08:00
common	HV: misra fix for patch set of Zephyr enabling	2019-06-06 09:40:52 +08:00
debug	xHV: remove unused function is_dbg_uart_enabled	2019-05-22 16:36:03 +08:00
dm	HV: remove cpu_num from vm configurations	2019-06-06 15:22:10 +08:00
hw	HV: remove function pci_pdev_foreach()	2019-05-23 14:06:51 +08:00
include	HV: remove unused INVALID_VM_ID	2019-06-06 15:22:10 +08:00
lib	1. fix cpu family calculation	2019-05-21 10:37:17 +08:00
pre_build	hv:merge static_checks.c	2019-05-14 09:16:33 +08:00
release	xHV: remove unused function is_dbg_uart_enabled	2019-05-22 16:36:03 +08:00
scenarios	HV: add hybrid scenario	2019-06-06 15:22:10 +08:00
scripts	hv: remove CONFIG_PLATFORM_[SBL\|UEFI] and UEFI_STUB	2019-03-13 10:26:55 +08:00
Kconfig	…
MAINTAINERS	…
Makefile	HV: add hybrid scenario	2019-06-06 15:22:10 +08:00
README.rst	doc: fix utf-8 punctuation, branding, spelling	2019-03-14 09:13:58 -07:00

README.rst

ACRN Hypervisor
###############

The open source `Project ACRN`_ defines a device hypervisor reference stack and
an architecture for running multiple software subsystems, managed securely, on
a consolidated system by means of a virtual machine manager. It also defines a
reference framework implementation for virtual device emulation, called the
"ACRN Device Model".

The ACRN Hypervisor is a Type 1 reference hypervisor stack, running directly on
the bare-metal hardware, and is suitable for a variety of IoT and embedded
device solutions. The ACRN hypervisor addresses the gap that currently exists
between datacenter hypervisors, and hard partitioning hypervisors. The ACRN
hypervisor architecture partitions the system into different functional
domains, with carefully selected guest OS sharing optimizations for IoT and
embedded devices.

You can find out more about Project ACRN on the `Project ACRN documentation`_
website.

.. _`Project ACRN`: https://projectacrn.org
.. _`ACRN Hypervisor`: https://github.com/projectacrn/acrn-hypervisor
.. _`Project ACRN documentation`: https://projectacrn.github.io/