Files
acrn-hypervisor/hypervisor
Jack Ren ff9d667b49 Refine the BSP/AP boot flowchart to match BIOS boot flow
This is only for the debug purpose. It is still unclear whether it can work on
ICL.

WhiskyLake BIOS will start APs and then each AP will call mwait to wait for BSP to
write monitor memory location to wake them up. Currently the hypervisor
will send SIPI to each AP and re-initialize them after the hypervisor
boots up. So APs can't respond to the wakeup requests from BSP anymore.

Fix: the hypervisor should send SIPI to the APs only after BIOS wakes up the AP.

Signed-off-by: Jack Ren <jack.ren@intel.com>
Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
2019-06-24 11:50:16 +08:00
..
2019-05-27 12:13:37 +08:00
2019-05-23 14:06:51 +08:00
2019-05-27 12:13:51 +08:00
2019-05-21 10:37:17 +08:00
2019-05-14 09:16:33 +08:00
2019-05-27 12:13:37 +08:00
2018-05-15 17:19:39 +08:00
2019-05-20 18:49:59 +08:00

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/