Steven Richman f32d0b48fd Use hypervisor abstraction to run VMs ... Calls to the kvm crate have been replaced by calls to hypervisor and devices::irqchip. Plugin is unchanged and still KVM-specific. x86 creates and configures vcpus on the vcpu thread instead of the main thread. Code that still depends on kvm or kvm_sys: - crosvm_plugin, plugin, and protos use kvm and kvm_sys if built with the plugin feature - devices::VfioGroup does a kvm_sys ioctl - devices::irqchip and hypervisor use kvm_sys. hypervisor uses kvm::Cap and kvm::CpuId internally for now. BUG=chromium:1077058 TEST=runs es2gears_wayland on kukui TEST=runs evince on amd64-generic with kernel and split irqchip TEST=build_test excluding tpm2 TEST=cargo check --features plugin Change-Id: I0068e34da6a5ff0079b1237be1958933bf12ffe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2307711 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Steven Richman <srichman@google.com>		2020-08-11 04:51:34 +00:00
..
src	Use hypervisor abstraction to run VMs	2020-08-11 04:51:34 +00:00
Cargo.toml	Use hypervisor abstraction to run VMs	2020-08-11 04:51:34 +00:00