commit | 05bd01793d82c740f5c4bd0c19eb69423382cb56 | [log] [tgz] |
---|---|---|
author | Alexandre Courbot <acourbot@chromium.org> | Wed Feb 16 07:02:12 2022 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 17 12:42:20 2022 |
tree | 03e21ff9283be5d1496f69b8c97e6d49b48b8acc | |
parent | 777348bbae8dab61d10060818771b947b2900732 [diff] |
devices: vvu: proxy: handle VIRTIO_MSI_NO_VECTOR The driver can send VIRTIO_MSI_NO_VECTOR as a MSI notification vector in order to indicate this vector should not be used. We are not using this currently but the spec mentions it. BUG=b:194136484 TEST=VVU-enabled console device works properly. Change-Id: I7023926b4acc8c46c193af6a4c3fb5b6d2383096 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3467299 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@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 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.