commit | 2dc11a85f2a1428959bbe7cf1ac167c107936246 | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Mon Apr 03 16:32:57 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 04 20:17:23 2023 +0000 |
tree | 9b2b8e4fe27e119ec69f38e18ee274e663edd507 | |
parent | 7e41126c86df16d28c994e99e5cc6e950ca819cf [diff] |
cros_async: delete Executor::async_from_local One `async_from` function can handle both `Send` and `!Send` IO sources now. Note that, before, when we were using `IoSourceExt`, having two functions for this wasn't really useful anyways because the returned trait object was always `!Send`. Change-Id: I2655657988b30a4fb4ec9c4ee543724d4e594de3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4391793 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Commit-Queue: Frederick Mayle <fmayle@google.com>
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.