mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-19 21:59:56 +00:00
e4a3a63496
Currently the SOS kernel will call hcall_set_callback_vector to config the expected up-notification vector(0xF3) and then hypervisor uses the passed vector to raise the interrupt to SOS when needed. As sos kernel already switches to 0xF3 notification vector, the default notification vector can be changed from 0xF7 to 0xF3. In such case it still can work well even when the SOS kernel doesn't reconfigure the notification vector. Tracked-On: projectacrn/acrn-hypervisor#2355 Acked-by: Eddie Dong <eddie.dong@intel.com> Signed-off-by: Zhao Yakui <yakui.zhao@intel.com> |
||
|---|---|---|
| .. | ||
| arch/x86 | ||
| boot | ||
| bsp | ||
| common | ||
| debug | ||
| dm | ||
| hw | ||
| include | ||
| lib | ||
| partition | ||
| release | ||
| scripts | ||
| Kconfig | ||
| MAINTAINERS | ||
| Makefile | ||
| 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/