commit | 6ba4551b434fcadb36570e96a4621e69208b0b42 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Mon Mar 07 16:19:58 2022 -0800 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 23 22:41:23 2022 +0000 |
tree | d8f69a234276416ffa572e309031625d880b7cf9 | |
parent | 4440db2370d563bafd4a13f431e977182e3d545e [diff] |
devices: vfio: remove unnecessary MemSlot casts The values that were cast in these expressions were already MemSlot, so there is no need to cast back and forth between MemSlot and u32. BUG=None TEST=tools/presubmit Change-Id: I8a215bc50d10a93b21f6d2fe7e4ed7267242a50b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3508320 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.