KVM: x86: Don't report guest userspace emulation error to userspace
authorNadav Amit <namit@cs.technion.ac.il>
Tue, 16 Sep 2014 23:50:50 +0000 (02:50 +0300)
committerBen Hutchings <ben@decadent.org.uk>
Thu, 1 Jan 2015 01:27:49 +0000 (01:27 +0000)
commit1aded21661bda559a407cfb7c69d0e53b72bc671
tree4a3f08b1134555a026b96a5a229167acc936847c
parent590461b16c5464b9d4377898abc057239a6afc3a
KVM: x86: Don't report guest userspace emulation error to userspace

commit a2b9e6c1a35afcc0973acb72e591c714e78885ff upstream.

Commit fc3a9157d314 ("KVM: X86: Don't report L2 emulation failures to
user-space") disabled the reporting of L2 (nested guest) emulation failures to
userspace due to race-condition between a vmexit and the instruction emulator.
The same rational applies also to userspace applications that are permitted by
the guest OS to access MMIO area or perform PIO.

This patch extends the current behavior - of injecting a #UD instead of
reporting it to userspace - also for guest userspace code.

Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
arch/x86/kvm/x86.c