commit | d37a6d71b96ce0b60a734322a94dd87eb7805f02 | [log] [tgz] |
---|---|---|
author | Shintaro Kawamura <kawasin@google.com> | Mon Dec 26 11:18:42 2022 +0900 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 10 02:58:54 2023 +0000 |
tree | a95f87a785dc47cd0c9298836728898b1179c30c | |
parent | fac92fad125e5fd796d6ef0dd798bb7dc1200fb3 [diff] |
swap: wake the faulting process on conflict userfaultfd does not wake the thread if zero operation fails with EEXIST. minor change: An unexpected page fault event is critical error because it blocks the faulting thread forever. BUG=b:215093219 TEST=none Change-Id: I5326878018f825024c7a5ceaf8daec5792547cb6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4125076 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: David Stevens <stevensd@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 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.