crosvm/hypervisor
Frederick Mayle 2a96ff0fb1 hypervisor: kvm: riscv64: don't mutate through a shared ref
When shared refs are used, the compiler may generate code that doesn't
witness the new value written via the pointer.

Change-Id: I6354fc3af749eaf7aaf1369c30b273371047d351
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5893919
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Frederick Mayle <fmayle@google.com>
2024-10-01 17:37:01 +00:00
..
hypervisor_test_macro
src hypervisor: kvm: riscv64: don't mutate through a shared ref 2024-10-01 17:37:01 +00:00
tests
Cargo.toml
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

  • Platforms: Linux
  • Tested upstream: yes

KVM is crosvm's preferred hypervisor for Linux.

WHPX

HAXM

Android Specific

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

Geniezone

Gunyah