commit | acfc8083f0c9bb7f0a61f910c2b41dac5dcbc9ca | [log] [tgz] |
---|---|---|
author | Tinghao Zhang <tinghao.zhang@intel.corp-partner.google.com> | Mon Mar 28 15:46:47 2022 +0800 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 31 00:49:28 2022 +0000 |
tree | aae53734e321795d6cd3291bae4131e4039bffbe | |
parent | 35d66b98172e3b9f761edd89bb243476c001e8ea [diff] |
devices: vfio_pci: make vfio msix cap shareable To emulate pending bit for MSI-X, we need to add a new interrupt delivery path in crosvm. We will make VfioPciWorker share vfio msix cap with VfioPciDevice, fire interrupt via msix cap when receiving irq from host device. This makes vfio msix cap shareable. BUG=None TEST=./tools/presubmit Change-Id: I77f5c377a41e7b2bd795e69c1ddcad9a9376f111 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3490238 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> 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 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.