commit | b180f9ce0fac7d9dc6eaa27adaecf93c2a3d6c13 | [log] [tgz] |
---|---|---|
author | Junichi Uekawa <uekawa@google.com> | Tue Dec 07 09:21:36 2021 +0900 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Dec 08 00:22:43 2021 +0000 |
tree | e3f6596320142558da0012c03625c15e77069f37 | |
parent | f18de38a022d6194e83b4b4fc84bfb3eb8cff3e7 [diff] |
crosvm: use BusRange in DirectIoOption. Used to use an unnamed tuple there but instead use the BusRange because it's semantic and now there's less copying. BUG=b:188011323 TEST=cargo test --features=direct Change-Id: I4a10251c758d330b8938090fb5971badcb9b7bdf Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3319716 Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Junichi Uekawa <uekawa@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.