commit | 5ad4a0e2fe1c17bc4bdeaef6a9f2ecdcbf914928 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Dec 09 16:45:39 2022 -0800 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 19 18:29:24 2023 +0000 |
tree | 0b298bb63cf00ce1ab73281cd37184ef77a3c11e | |
parent | 85ee3b4900bfa7fdfa356bd32c8580aa8eb321f4 [diff] |
devices: virtio: vhost-user: ack queue features in common code Each VhostUserBackend::start_queue() implementation had its own call to queue.ack_features(), which we can factor out into the single place that calls start_queue(). BUG=None TEST=tools/presubmit --all Change-Id: I2889f5927f6beff55bfc1d89d366da5fcaccd063 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4111871 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> 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.