mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-24 20:48:55 +00:00

History

Daniel Verkamp d83234fcf7 hypervisor: remove unused Vcpu functions These Vcpu functions are never called anywhere (some were previously used but the uses have been removed; some were part of the initial hypervisor API port and were never used): - get_hyperv_cpuid() - handle_hyperv_hypercall() - handle_rdmsr() - handle_wrmsr() Additionally, these KVM-specific VM functions that are no longer called can be removed (related to the handle_rdrmsr/handle_wrmsr functions): - enable_userspace_msr() - set_msr_filter() Remove the dead code (including the corresponding VcpuExit codes where relevant) to simplify the Vcpu API. If these are ever re-added, they should be implemented on VcpuX86_64 rather than the generic Vcpu, as they are x86-specific features. BUG=b:337131577 TEST=tools/dev_container tools/presubmit Change-Id: I0187127170b30d7720212e26a84fd06773c824c4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5499407 Reviewed-by: Idan Raiter <idanr@google.com> Reviewed-by: Noah Gold <nkgold@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>		2024-05-07 18:22:14 +00:00
..
src	hypervisor: remove unused Vcpu functions	2024-05-07 18:22:14 +00:00
tests	hypervisor: remove unused Vcpu functions	2024-05-07 18:22:14 +00:00
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

KVM is crosvm's preferred hypervisor for Linux.

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