mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-02-22 07:02:35 +00:00
Replace SBI passthrough with proper virtualization of base extension queries. For the Service VM, forward actual machine vendor/arch/impl IDs from the underlying SBI. For guest VMs, provide dummy ACRN-specific IDs to maintain isolation. Changes: - Return vSBI spec version 2.0 for GET_SPEC_VERSION - Return ACRN implementation ID (55) and version for GET_IMP_ID/GET_IMP_VERSION - Forward real mvendorid/marchid/mimpid to Service VM - Provide dummy vendor/arch/impl IDs (0/0/0) to guest VMs - Store machine IDs in vm_arch structure during VM initialization - Remove unnecessary SBI passthrough for base extension queries This provides better isolation and control over the virtual SBI interface exposed to guests. Tracked-On: #8851 Signed-off-by: Haoyu Tang <haoyu.tang@intel.com> Acked-by: Wang Yu1 <yu1.wang@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/