mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-12-16 09:52:28 +00:00
dba49b38df
Suppose the current vcpu is 0, the other vcpus (1, 2, 3) may wait on the "get_split_lock", the current vcpu need clear the ACRN_REQUEST_SPLIT_LOCK explicitly here after finishing the emulation. Otherwise, it make cause dead lock. for example: 1. Once vcpu 0 "put_split_lock", let's say vcpu 1 will "get_split_lock". 2. vcpu 1 call "vcpu_make_request" to pause vcpu 0, 2, 3. 3. vcpu 1's VCPU_EVENT_SPLIT_LOCK is still not cleared because the vcpu 0 called "vcpu_make_request" ever. 4. All vcpus will wait for VCPU_EVENT_SPLIT_LOCK in acrn_handle_pending_request. We should avoid this dead lock case. Please note: this patch is only for release 2.5 test. Tracked-On: #6051 Signed-off-by: Jie Deng <jie.deng@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/