mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-05-04 17:58:48 +00:00
3e1fa0fb98
So that DM can retrieve physical APIC IDs and use them to fill in the ACPI MADT table for post-launched VMs. Note: 1. DM needs to use the same logic as hypervisor to calculate vLAPIC IDs based on physical APIC IDs and CPU affinity setting 2. Using reserved0[] in struct hc_platform_info to pass physical APIC IDs means we can only support at most 116 cores. And it assumes LAPIC ID is 8bits (X2APIC mode supports 32 bits). Cat IDs shift will be used by DM RTCT V2 Tracked-On: #6020 Reviewed-by: Wang, Yu1 <yu1.wang@intel.com> Signed-off-by: dongshen <dongsheng.x.zhang@intel.com>
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/