mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-05-05 12:22:53 +00:00
db83648a8d
Thermal events are delivered through lapic thermal LVT. Currently ACRN does not support delivering those interrupts to guests by virtual lapic. They need to be virtualized to provide guests some thermal management abilities. Currently we just hide thermal lvt from guests, including: 1. Thermal LVT: There is no way to hide thermal LVT from guests. But we need do something to make sure no interrupt can be actually trigered: - skip thermal LVT in vlapic_trigger_lvt() - trap-and-emulate thermal LVT in lapic-pt mode 2. As We have plan to introduce virtualization of thermal monitor in the future, we use a vm flag GUEST_FLAG_VTM which is default 0 to control the access to it. So that it can help enabling VTM in the future. Tracked-On: #8414 Signed-off-by: Wu Zhou <wu.zhou@intel.com> Reviewed-by: Junjie Mao <junjie.mao@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/