Sean Christopherson f78d0971b7 KVM: VMX: Don't save guest registers after VM-Fail ... A failed VM-Enter (obviously) didn't succeed, meaning the CPU never executed an instrunction in guest mode and so can't have changed the general purpose registers. In addition to saving some instructions in the VM-Fail case, this also provides a separate path entirely and thus an opportunity to propagate the fail condition to vmx->fail via register without introducing undue pain. Using a register, as opposed to directly referencing vmx->fail, eliminates the need to pass the offset of 'fail', which will simplify moving the code to proper assembly in future patches. Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2019-02-12 13:12:26 +01:00
..
capabilities.h
evmcs.c	x86/kvm/hyper-v: nested_enable_evmcs() sets vmcs_version incorrectly	2019-01-25 19:11:37 +01:00
evmcs.h
nested.c	KVM: nVMX: Cache host_rsp on a per-VMCS basis	2019-02-12 13:12:22 +01:00
nested.h
ops.h
pmu_intel.c
vmcs12.c
vmcs12.h
vmcs_shadow_fields.h
vmcs.h	KVM: nVMX: Cache host_rsp on a per-VMCS basis	2019-02-12 13:12:22 +01:00
vmenter.S
vmx.c	KVM: VMX: Don't save guest registers after VM-Fail	2019-02-12 13:12:26 +01:00
vmx.h	KVM: VMX: Pass "launched" directly to the vCPU-run asm blob	2019-02-12 13:12:24 +01:00