mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-05 18:20:34 +00:00
No description
7b13ef3ea6
Based on the previous proposal in [1]. * The Executor is now completely platform-agnostic and only relies on the platform to provide a type that implements the `PlatformState` trait. * The crate provides concrete high-level types rather than forcing users to deal with trait objects and async-trait. Currently, only File and Event are supported. Support for timers, sockets, and pipes will be added in subsequent changes. * Each high-level type delegates the implementation to a platform-specific type and exists mainly as a place to hold documentation and tests. * On Unix the io_driver module provides async versions of various IO-related syscalls, which are used by the platform-specific File and Event types to implement the required behavior. * io-uring support can be disabled at compile time. When uring support is enabled, we make a runtime check to decide whether or not to use it. The actual io-uring driver is currently unimplemented and will be added in a subsequent change. One non-trivial downside of this change is that the futures returned by the various async methods are !Send and !Sync, which means that they can only be awaited from the same thread on which they were started. In practice this should be fine since current crosvm (and Chrome OS) code doesn't really make use of sending futures to different threads. This can also be mitigated by using `Executor::spawn_local` and a `oneshot::channel` to isolate the !Send future from the outer async fn (as long as the output of the future is Send). See the crate documentation and the `outer_future_is_send` test in `src/executor.rs` for more details. [1]: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3062166 BUG=b:195468578 TEST=unit tests Change-Id: I1aad0885e67a957149e2ec3b4d9df215d9b20d81 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3222223 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Chirantan Ekbote <chirantan@chromium.org> |
||
|---|---|---|
| .cargo | ||
| .devcontainer | ||
| .github | ||
| aarch64 | ||
| acpi_tables | ||
| arch | ||
| bin | ||
| bit_field | ||
| ci/kokoro | ||
| common | ||
| crosvm-fuzz | ||
| crosvm_plugin | ||
| devices | ||
| disk | ||
| docs/book | ||
| fuse | ||
| gpu_display | ||
| hypervisor | ||
| integration_tests | ||
| kernel_cmdline | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| libcras_stub | ||
| libcrosvm_control | ||
| libvda | ||
| linux_input_sys | ||
| logo | ||
| net_sys | ||
| net_util | ||
| power_monitor | ||
| protos | ||
| qcow_utils | ||
| resources | ||
| rutabaga_gfx | ||
| seccomp | ||
| src | ||
| system_api_stub | ||
| tests | ||
| third_party | ||
| tools | ||
| tpm2 | ||
| tpm2-sys | ||
| usb_sys | ||
| usb_util | ||
| vfio_sys | ||
| vhost | ||
| virtio_sys | ||
| vm_control | ||
| vm_memory | ||
| x86_64 | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| ARCHITECTURE.md | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| navbar.md | ||
| OWNERS | ||
| README.chromeos | ||
| README.md | ||
| run_tests | ||
| rust-toolchain | ||
| setup_cros_cargo.sh | ||
| test_all | ||
| unblocked_terms.txt | ||
crosvm - The Chrome OS Virtual Machine Monitor
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 Chrome OS 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 Chrome OS devices.
- Documentation
- Source code
- API doc, useful for searching API.
- For contribution, see the contributor guide. Mirror repository is available at GitHub for your convenience, but we don't accept bug reports or pull requests there.
- Issue tracker
