mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-10-09 03:08:52 +00:00
f0244b24e7
Replace new_base with vbar_base in vdev_pt_remap_generic_mem_vbar(). We will call vdev_pt_remap_generic_mem_vbar() after a new vbar base is set, no need to pass new_base to vdev_pt_remap_generic_mem_vbar(), as this new vbar base (vbar_base) can be obtained by calling get_vbar_base(). The reason we call vdev_pt_remap_generic_mem_vbar() after a new vbar base is set is for 64-bit mmio handling: when the lower 32-bit of 64-bit mmio vbar is set, we will defer calling vdev_pt_remap_generic_mem_vbar until its upper 32-bit vbar base is set. Tracked-On: #3241 Signed-off-by: dongshen <dongsheng.x.zhang@intel.com> Reviewed-by: Eddie Dong <eddie.dong@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/