commit | f2eec5cadae6d3bd3f71d1129304489e947f1b8e | [log] [tgz] |
---|---|---|
author | Elliot Berman <quic_eberman@quicinc.com> | Wed Mar 20 09:56:59 2024 -0700 |
committer | Elliot Berman <quic_eberman@quicinc.com> | Mon Apr 29 08:20:33 2024 -0700 |
tree | 6ceff9a9cd3a7a078ac72b9ef046d107c70b0305 | |
parent | b644b7e5879df0dcc65a542102c768d64aa51b84 [diff] |
hypervisor: gunyah: Mark shm devices as optional When using demand paging, userspace shouldn't provide shm vdevice in the VM configuration. The shm vdevice is used by RM to automatically accept and map the mem parcel. With demand paging, the kernel wouldn't be creating mem parcels and Gunyah complains about that no mem parcel was provided for the shm vdevice. Gunyah allows us to add "optional" tag to the vdevice and it will be ignored if no mem parcel is prvoided, as is the case for demand paging. We could create additional downstream UAPI to indicate whether demand paging is being used and not create the vdevice node at all, but the approach of adding "optional" property was preferred to avoid creating downstream UAPI. Bug: 330496811 Change-Id: Ib070e9d453af88a7af5f8c240f9a22c7b744c987 Signed-off-by: Elliot Berman <quic_eberman@quicinc.com>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on ChromeOS devices.