Jim Mattson 1aa561b1a4 kvm: x86: Add "last CPU" to some KVM_EXIT information ... More often than not, a failed VM-entry in an x86 production environment is induced by a defective CPU. To help identify the bad hardware, include the id of the last logical CPU to run a vCPU in the information provided to userspace on a KVM exit for failed VM-entry or for KVM internal errors not associated with emulation. The presence of this additional information is indicated by a new capability, KVM_CAP_LAST_CPU. Signed-off-by: Jim Mattson <jmattson@google.com> Reviewed-by: Oliver Upton <oupton@google.com> Reviewed-by: Peter Shier <pshier@google.com> Message-Id: <20200603235623.245638-5-jmattson@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2020-07-08 16:21:45 -04:00
..
avic.c	KVM: SVM: Move AVIC code to separate file	2020-04-03 10:53:56 -04:00
nested.c	KVM: nSVM: Check that DR6[63:32] and DR7[64:32] are not set on vmrun of nested guests	2020-07-08 16:21:41 -04:00
pmu.c	KVM: x86/pmu: Tweak kvm_pmu_get_msr to pass 'struct msr_data' in	2020-06-01 04:26:08 -04:00
sev.c	kvm: svm: Always set svm->last_cpu on VMRUN	2020-07-08 16:21:43 -04:00
svm.c	kvm: x86: Add "last CPU" to some KVM_EXIT information	2020-07-08 16:21:45 -04:00
svm.h	KVM: nSVM: leave guest mode when clearing EFER.SVME	2020-06-01 04:26:03 -04:00
vmenter.S	KVM: SVM: Do not setup frame pointer in __svm_vcpu_run	2020-04-15 12:08:38 -04:00