diff options
author | Brijesh Singh <brijesh.singh@amd.com> | 2017-12-04 17:57:40 +0100 |
---|---|---|
committer | Brijesh Singh <brijesh.singh@amd.com> | 2017-12-04 20:33:14 +0100 |
commit | 00b10fe1046c4b2232097a7ffaa9238c7e479388 (patch) | |
tree | 97baced4011d1ffdc3c76d3b36f3090741959c59 /net/vmw_vsock | |
parent | KVM: SVM: Do not install #UD intercept when SEV is enabled (diff) | |
download | linux-00b10fe1046c4b2232097a7ffaa9238c7e479388.tar.xz linux-00b10fe1046c4b2232097a7ffaa9238c7e479388.zip |
KVM: X86: Restart the guest when insn_len is zero and SEV is enabled
On AMD platforms, under certain conditions insn_len may be zero on #NPF.
This can happen if a guest gets a page-fault on data access but the HW
table walker is not able to read the instruction page (e.g instruction
page is not present in memory).
Typically, when insn_len is zero, x86_emulate_instruction() walks the
guest page table and fetches the instruction bytes from guest memory.
When SEV is enabled, the guest memory is encrypted with guest-specific
key hence hypervisor will not able to fetch the instruction bytes.
In those cases we simply restart the guest.
I have encountered this issue when running kernbench inside the guest.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Joerg Roedel <joro@8bytes.org>
Cc: Borislav Petkov <bp@suse.de>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Cc: x86@kernel.org
Cc: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
Diffstat (limited to 'net/vmw_vsock')
0 files changed, 0 insertions, 0 deletions