commit | 64a3fc2d085c9b2468478da63be30b62911fa156 | [log] [tgz] |
---|---|---|
author | Alexandre Courbot <acourbot@chromium.org> | Thu Apr 14 05:58:10 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 27 06:53:06 2022 |
tree | c0526b9da5e28ef1e4aeebcdf219e87cca03f0e6 | |
parent | c9b84cf5702ef9476f42db64e52d908b08954b17 [diff] |
devices: vhost-user: remove Arc from SlaveListener and SlaveReqHandler The SlaveReqHandler should be the sole owner of a VhostUserBackend since it calls its mutable methods, so we shouldn't need an Arc here. If sharing is necessary users can use their own locking mechanism. Single ownership will help to retrieve the backend after a client disconnects, to reuse it for another connection if needed. BUG=b:229554679 BUG=b:216407443 TEST=cargo test -p vmm_vhost TEST=vhost-user console device works. TEST=cargo test -p devices Change-Id: I2358c807ac3ddb1ee4b29d97df0ade5a3e30a85a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3591108 Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Richard Zhang <rizhang@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@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 Chrome OS 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 Chrome OS devices.