mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-03-18 11:04:12 +00:00
bbe8e254cf
Currently ivshmem device can only be configurated as single function device(bdf.f = 0) on bus 0. This greatly limits the number of ivshmem devices we can create. This patch is to enable multiple function bit in HEADER_TYPE config register, so that we can create many more ivshmem devices by using different function numbers on one bus:dev. The multi function device bit is to be set on ivshmem devices whose function number equls 0. PCI spec describe it as: ‘When Set, indicates that the Device may contain multiple Functions, but not necessarily.’, So if this dev is the only one on the bus:dev, it is still OK. Tracked-On: #8520 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/