10474ae894
X86 CPUs need to have some magic happening to enable the virtualization extensions on them. This magic can result in unpleasant results for users, like blocking other VMMs from working (vmx) or using invalid TLB entries (svm). Currently KVM activates virtualization when the respective kernel module is loaded. This blocks us from autoloading KVM modules without breaking other VMMs. To circumvent this problem at least a bit, this patch introduces on demand activation of virtualization. This means, that instead virtualization is enabled on creation of the first virtual machine and disabled on destruction of the last one. So using this, KVM can be easily autoloaded, while keeping other hypervisors usable. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com> |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
asm-offsets.c | ||
irq.h | ||
kvm-ia64.c | ||
kvm_fw.c | ||
kvm_lib.c | ||
kvm_minstate.h | ||
lapic.h | ||
memcpy.S | ||
memset.S | ||
misc.h | ||
mmio.c | ||
optvfault.S | ||
process.c | ||
trampoline.S | ||
vcpu.c | ||
vcpu.h | ||
vmm.c | ||
vmm_ivt.S | ||
vti.h | ||
vtlb.c |