commit | 1cb82fdb359fa7ce1cd86913376fe611b639bca7 | [log] [tgz] |
---|---|---|
author | Alexandre Courbot <acourbot@chromium.org> | Tue Mar 29 21:38:34 2022 +0900 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Apr 03 12:45:07 2022 +0000 |
tree | 1749b4017426080330174689526c401b93b5117f | |
parent | f9eb7f26ea8b0c2926efc1b4d5ee804162d7046a [diff] |
devices: vvu: handler: only pass needed data to HandlerType When using VVU, the DeviceRequestHandler only needs a reference to the VFIO device, the PCI caps, and the notification events. There is no need to share a reference to the whole VvuPciDevice, and releasing that reference will actually allow us to remove it as well as the VvuPciDevice mutex in a future CL. BUG=b:194137301 TEST=VVU block device works. Change-Id: I077c053af8ddefa4b0d624fe6775b5072e843686 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3565620 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.