Files
acrn-hypervisor/hypervisor
Yi Sun 37b1c13f95 hv: pci: refine codes to make Service VM can manage bridge
In previous codes, the bridge is owned by hypervsior if there
is pre-launched VM configured. This can cause bug, e.g. the
net card behind the bridge cannot get IP because the write
to bridge's command register to set BusMaster bit is ignored.

This patch is to refine the codes to make the bridge be managed
by Service VM if the device behind the bridge is not assigned to
pre-launched VM. Furthermore, it adds the parent device into struct
pci_pdev to construct PCI hierarchy.

Tracked-On: #8849
Signed-off-by: Yi Sun <yi.y.sun@intel.com>
2025-12-01 17:11:20 +08:00
..
2025-09-05 12:31:42 +08:00
2024-05-16 09:40:32 +08:00

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/