| commit | e6c584f08d2e6ff37afa9c3819289c41130c6bc6 | [log] [tgz] |
|---|---|---|
| author | Frederick Mayle <fmayle@google.com> | Fri Apr 07 01:41:14 2023 |
| committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 19 08:44:15 2023 |
| tree | 6e1da9f57a1f39e78f45bc7971c5f670c8f70aec | |
| parent | b7f68c53517247813b3de98d2233cf65273054ed [diff] |
cros_async: trim IoSource API `wait_for_handle` only makes sense on Windows. `read_u64` can be implemented in terms of the other read methods. We now have to allocate a `Vec` which shouldn't technically be needed for the epoll backend. We do this for all other kinds of IO and timers/events are generally low throughput, so expect the performance loss won't be noticable. Change-Id: I1c1f1d5d1fc84073b940bc71425fe150196c4441 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4405314 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.
