commit | ffcf8ee27ebf7142fcecd5b9032b81707d1b5b01 | [log] [tgz] |
---|---|---|
author | Elie Kheirallah <khei@google.com> | Tue Jul 18 15:25:54 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 18 20:10:33 2023 +0000 |
tree | f46b90f4f5d2062e541daa7434d1a291670e9f3c | |
parent | ef01e01adc654169d71bfd0d8c991ae0eadb9ceb [diff] |
devices: virtio: wl: add wake Add virtio-wake to Wl device as part of the sleep/wake/snapshot/restore efforts. BUG=b:232437513 TEST=presubmit Change-Id: I8893ceb3bcf9fc45a699c00a7ed7e8189f5cf4e6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4695653 Commit-Queue: Elie Kheirallah <khei@google.com> Reviewed-by: 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.