commit | 4fe7944e35d11924727f52114c93ffebdee6d398 | [log] [tgz] |
---|---|---|
author | Shintaro Kawamura <kawasin@google.com> | Mon Mar 13 18:10:15 2023 +0900 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 14 02:12:16 2023 +0000 |
tree | fbf7a5783a7c79af8b6436e6be78e4931704daf1 | |
parent | c0e2630d69b903f2e885bf13ebcc7b407c185c17 [diff] |
swap: use Lazy::force instead of dereference As you can see in the doc comment of `Lazy::force()`, `Lazy::force()` "is equivalent to the `Deref` impl, but is explicit". BUG=none TEST=manual test Change-Id: I77b5e6ab1985e7efe1bdb86eefb5271438c451fa Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4333208 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
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 ChromeOS 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 ChromeOS devices.