commit | 882890f47a51f1c670b2084a89ab89a8a4ecc645 | [log] [tgz] |
---|---|---|
author | Richard Zhang <rizhang@google.com> | Thu May 18 01:22:12 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 19 17:56:12 2023 +0000 |
tree | b15400e3abd759079030eb13917513d297742a42 | |
parent | 4c7130dc043288c2c8daf4dd1ea074c7c9918004 [diff] |
vhost-user: return the active Queue from stop_queue Most of this change involves wrapping the Queue object inside an Rc<RefCell<>>, Arc<Mutex<>>, or Rc<AsyncMutex<>>. This is necessary for getting device suspend and resume to work. Bug=280607608 TEST=presubmits Change-Id: I7e3680aea2927c1fc9d971f27ebbb09ec308a634 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4545603 Commit-Queue: Richard Zhang <rizhang@google.com> Reviewed-by: Noah Gold <nkgold@google.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.