commit | 67ec31272bbc0d0c44159b3d76d8158dda345af7 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Mon Jul 31 11:03:14 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 01 18:35:15 2023 +0000 |
tree | 1aef6c8f8ef1aa233eaaf641489e7fa0dcf3a2bc | |
parent | 3cf71cbbb167e9ed7e82f91cc8c877a9678271b2 [diff] |
devices: virtio: use QueueConfig in Queue::restore() Use the negotiated feature bits in QueueConfig to determine the queue type for activated queues when restoring from a snapshot. This also means that VirtioDevice::queue_type() is unused, so it can be removed. BUG=b:243621596 TEST=tools/dev_container tools/presubmit Change-Id: I15be4c0a0794f28ff36cb3c0e6149b45ea90e2ad Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4735113 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Yuan Yao <yuanyaogoog@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.