KVM: nVMX: No need for handle_vmx_insn function any more
authorNadav Har'El <nyh@il.ibm.com>
Wed, 25 May 2011 20:11:03 +0000 (23:11 +0300)
committerAvi Kivity <avi@redhat.com>
Tue, 12 Jul 2011 08:45:15 +0000 (11:45 +0300)
Before nested VMX support, the exit handler for a guest executing a VMX
instruction (vmclear, vmlaunch, vmptrld, vmptrst, vmread, vmread, vmresume,
vmwrite, vmon, vmoff), was handle_vmx_insn(). This handler simply threw a #UD
exception. Now that all these exit reasons are properly handled (and emulate
the respective VMX instruction), nothing calls this dummy handler and it can
be removed.

Signed-off-by: Nadav Har'El <nyh@il.ibm.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
arch/x86/kvm/vmx.c

index 1a8b32867975eae0da9c210e574fa3dd08899a82..f8dccb9df34bcea35f9b8bb84ff6a4ee34e573dc 100644 (file)
@@ -4309,12 +4309,6 @@ static int handle_vmcall(struct kvm_vcpu *vcpu)
        return 1;
 }
 
-static int handle_vmx_insn(struct kvm_vcpu *vcpu)
-{
-       kvm_queue_exception(vcpu, UD_VECTOR);
-       return 1;
-}
-
 static int handle_invd(struct kvm_vcpu *vcpu)
 {
        return emulate_instruction(vcpu, 0) == EMULATE_DONE;