commit | abfe4b5a53ffd10d8de1e9dd23d37079dc206d15 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Feb 25 14:45:05 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Feb 28 19:16:40 2022 +0000 |
tree | a772e9a40c7a35d4a48ee2ceb2ad1e08c15ec39a | |
parent | 6bbdcb9e907f95fcb9b638c5f80bc9ed77145f15 [diff] |
devices: virtio: video: fix build with base MemoryMapping The base version of MemoryMapping does not have the from_fd_offset function. Use base::MemoryMappingBuilder and MemoryMappingBuilderUnix to get the same functionality without depending directly on sys_util. Fixes the build with virtio video features enabled. BUG=b:213149154 TEST=emerge-hatch crosvm Fixes: 45f1a419d429 ("Make crates depend on base instead of sys_util") Change-Id: I8924d2334ae3d3ef489114b17071143871d1424d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3490743 Reviewed-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Alexandre Courbot <acourbot@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.