commit | b5f8224312cfb65f4d7e339030d61342471dd505 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri May 06 23:36:12 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 11 17:56:27 2022 |
tree | e538975cc3e54d35236950242205aea082e8c5e3 | |
parent | 8212e88f839411ae82fb17ffa28f8076e4b5759d [diff] |
base: windows: use sync::Mutex to avoid unwrap() Switch the uses of std::sync::Mutex to our custom sync::Mutex, which panics internally if lock() fails. This helps to reduce the instances of unwrap(), making it easier to review and understand the code. BUG=b:213153157 TEST=tools/dev_container tools/run_tests --target=host --arch=win64 Change-Id: I99bfc85967152f50045e64293104de788a5d3829 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3633108 Reviewed-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Noah Gold <nkgold@google.com> 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.