commit | b3c8e72a4913aeefd7076d2f061115a09e709227 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Jul 07 14:54:13 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 01 21:45:08 2023 +0000 |
tree | 930255a026c37cb0619a2f88aad2f18b7106f983 | |
parent | 35828a105f6f0c5bccbf20439f03dbfba358d269 [diff] |
devices: virtio: pass GuestMemory to queue activate Now that an active Queue is a separate type than the pre-activation QueueConfig, we can ensure that a Queue has a valid reference to the GuestMemory at creation time instead of passing it to every queue operation. No functional change, but simplifies Queue callers and prepares for use of AtomicU* types in a later change. BUG=b:264931437 TEST=tools/dev_container tools/presubmit Change-Id: I30266a5eadbd4f643da5595fbdd2c8f5df34bab3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4671481 Reviewed-by: Frederick Mayle <fmayle@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
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.