mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-24 12:34:31 +00:00

History

Daniel Verkamp 8d06f7a776 hypervisor: tests: add REP INSB/OUTSB test This tests repeated I/O string instructions call the handle_io callback the correct number of times with the expected size. BUG=b:283990685 Change-Id: Ia8b55c7059082376d6cdd825224f362f46bd0ea2 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5798664 Reviewed-by: Oystein Eftevaag <oysteine@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Judson Powers <judsonp@google.com>		2024-10-07 17:38:25 +00:00
..
hypervisor_test_macro
src	hypervisor: haxm: fix repeated port IO (REP OUTSB etc.)	2024-10-07 17:38:19 +00:00
tests	hypervisor: tests: add REP INSB/OUTSB test	2024-10-07 17:38:25 +00:00
Cargo.toml	hypervisor: add gvm feature to Cargo.toml	2024-10-01 02:17:20 +00:00
README.md

Hypervisor Support

Multiple hypervisor backends are supported. See Advanced Usage for overriding the default backend.

Hypervisors added to crosvm must meet the following requirements:

Hypervisor code must be buildable in crosvm upstream.
- Within reason, crosvm maintainers will ensure the hypervisor's code continues to build.
Hypervisors are not required to be tested upstream.
- We can't require testing upstream because some hypervisors require specialized hardware.
- When not tested upstream, the hypervisor's maintainers are expected to test it downstream. If a change to crosvm breaks something downstream, then the hypervisor's maintainers are expected to supply the fix and can't expect a revert of the culprit change to be accepted upstream.

KVM

KVM is crosvm's preferred hypervisor for Linux.

The hypervisors in this section are used as backends of the Android Virtualization Framework.