Searched hist:"696 ca779a928d0e93d61c38ffc3a4d8914a9b9a0" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/arch/x86/kvm/ |
| H A D | hyperv.c | diff 696ca779a928d0e93d61c38ffc3a4d8914a9b9a0 Thu May 24 10:50:56 CDT 2018 Radim Krčmář <rkrcmar@redhat.com> KVM: x86: fix #UD address of failed Hyper-V hypercalls
If the hypercall was called from userspace or real mode, KVM injects #UD
and then advances RIP, so it looks like #UD was caused by the following
instruction. This probably won't cause more than confusion, but could
give an unexpected access to guest OS' instruction emulator.
Also, refactor the code to count hv hypercalls that were handled by the
virt userspace.
Fixes: 6356ee0c9602 ("x86: Delay skip of emulated hypercall instruction")
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
|
| H A D | x86.c | diff 696ca779a928d0e93d61c38ffc3a4d8914a9b9a0 Thu May 24 10:50:56 CDT 2018 Radim Krčmář <rkrcmar@redhat.com> KVM: x86: fix #UD address of failed Hyper-V hypercalls
If the hypercall was called from userspace or real mode, KVM injects #UD
and then advances RIP, so it looks like #UD was caused by the following
instruction. This probably won't cause more than confusion, but could
give an unexpected access to guest OS' instruction emulator.
Also, refactor the code to count hv hypercalls that were handled by the
virt userspace.
Fixes: 6356ee0c9602 ("x86: Delay skip of emulated hypercall instruction")
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
|