mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-07-30 13:53:54 -06:00
e6c33efed3
Add a new device, ivshmem-flat, which is similar to the ivshmem PCI but does not require a PCI bus. It's meant to be used on machines like those with Cortex-M MCUs, which usually lack a PCI/PCIe bus, e.g. lm3s6965evb and mps2-an385. The device currently only supports the sysbus bus. The new device, just like the ivshmem PCI device, supports both peer notification via hardware interrupts and shared memory. The device shared memory size can be set using the 'shmem-size' option and it defaults to 4 MiB, which is the default size of shmem allocated by the ivshmem server. Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1134 Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org> [PMD: Rebased updating Property and using DEFINE_TYPES macro] Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org> Message-ID: <20241216141818.111255-2-gustavo.romero@linaro.org>
33 lines
1.9 KiB
ReStructuredText
33 lines
1.9 KiB
ReStructuredText
Inter-VM Shared Memory Flat Device
|
|
----------------------------------
|
|
|
|
The ivshmem-flat device is meant to be used on machines that lack a PCI bus,
|
|
making them unsuitable for the use of the traditional ivshmem device modeled as
|
|
a PCI device. Machines like those with a Cortex-M MCU are good candidates to use
|
|
the ivshmem-flat device. Also, since the flat version maps the control and
|
|
status registers directly to the memory, it requires a quite tiny "device
|
|
driver" to interact with other VMs, which is useful in some RTOSes, like
|
|
Zephyr, which usually run on constrained resource targets.
|
|
|
|
Similar to the ivshmem device, the ivshmem-flat device supports both peer
|
|
notification via HW interrupts and Inter-VM shared memory. This allows the
|
|
device to be used together with the traditional ivshmem, enabling communication
|
|
between, for instance, an aarch64 VM (using the traditional ivshmem device and
|
|
running Linux), and an arm VM (using the ivshmem-flat device and running Zephyr
|
|
instead).
|
|
|
|
The ivshmem-flat device does not support the use of a ``memdev`` option (see
|
|
ivshmem.rst for more details). It relies on the ivshmem server to create and
|
|
distribute the proper shared memory file descriptor and the eventfd(s) to notify
|
|
(interrupt) the peers. Therefore, to use this device, it is always necessary to
|
|
have an ivshmem server up and running for proper device creation.
|
|
|
|
Although the ivshmem-flat supports both peer notification (interrupts) and
|
|
shared memory, the interrupt mechanism is optional. If no input IRQ is
|
|
specified for the device it is disabled, preventing the VM from notifying or
|
|
being notified by other VMs (a warning will be displayed to the user to inform
|
|
the IRQ mechanism is disabled). The shared memory region is always present.
|
|
|
|
The MMRs (INTRMASK, INTRSTATUS, IVPOSITION, and DOORBELL registers) offsets at
|
|
the MMR region, and their functions, follow the ivshmem spec, so they work
|
|
exactly as in the ivshmem PCI device (see ./specs/ivshmem-spec.txt).
|