commit | 223c1fb7c7df72ad318d4916dea829db797ef9f2 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Tue Mar 28 23:27:37 2023 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 12 19:41:17 2023 |
tree | 8366cef14c24f0733ceb00f08c386a463c5e1db8 | |
parent | 7781380f01e32b67021a55a06cccfd915b00bbaa [diff] |
unix: require hypervisor ImmediateExit capability Remove the fallback path that supported old KVM versions without KVM_CAP_IMMEDIATE_EXIT, which has been available since Linux 4.11 / commit 460df4c1fc7c ("KVM: race-free exit from KVM_RUN without POSIX signals"). This also removes the need for the Vcpu::set_signal_mask() function, so it is removed from all hypervisors. BUG=b:281723434 TEST=boot crosvm on device with 4.14 host kernel Change-Id: I5329d9b5a6aef6ddac4797aa7ef291df333d27f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4382339 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> 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 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.