aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorSheng Yang <sheng@linux.intel.com>2010-01-19 04:43:21 -0500
committerMarcelo Tosatti <mtosatti@redhat.com>2010-03-01 10:36:01 -0500
commit7062dcaa369cae40c1a59949a5654985d0ae26ea (patch)
tree60dc5981d55a8544720b38b89e8d127a78e18ec6 /arch
parent94718da12741ef44e1eb2bfe3ca37db92115a3d3 (diff)
KVM: VMX: Remove emulation failure report
As Avi noted: >There are two problems with the kernel failure report. First, it >doesn't report enough data - registers, surrounding instructions, etc. >that are needed to explain what is going on. Second, it can flood >dmesg, which is a pretty bad thing to do. So we remove the emulation failure report in handle_invalid_guest_state(), and would inspected the guest using userspace tool in the future. Signed-off-by: Sheng Yang <sheng@linux.intel.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/x86/kvm/vmx.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index fc1964d5e97c..516084f3c6d8 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -3449,7 +3449,6 @@ static int handle_invalid_guest_state(struct kvm_vcpu *vcpu)
3449 } 3449 }
3450 3450
3451 if (err != EMULATE_DONE) { 3451 if (err != EMULATE_DONE) {
3452 kvm_report_emulation_failure(vcpu, "emulation failure");
3453 vcpu->run->exit_reason = KVM_EXIT_INTERNAL_ERROR; 3452 vcpu->run->exit_reason = KVM_EXIT_INTERNAL_ERROR;
3454 vcpu->run->internal.suberror = KVM_INTERNAL_ERROR_EMULATION; 3453 vcpu->run->internal.suberror = KVM_INTERNAL_ERROR_EMULATION;
3455 vcpu->run->internal.ndata = 0; 3454 vcpu->run->internal.ndata = 0;