summaryrefslogtreecommitdiff
path: root/arch/sparc/Makefile
diff options
context:
space:
mode:
authorTom Lendacky <thomas.lendacky@amd.com>2021-05-24 20:48:57 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2021-11-18 10:12:13 +0300
commitb5aead0064f33ae5e693a364e3204fe1c0ac9af2 (patch)
tree08239ad26b767f683a105e0c0c88abed4520edaf /arch/sparc/Makefile
parentb768f60bd9791c528a4a4b98659674787b2e7c63 (diff)
downloadlinux-b5aead0064f33ae5e693a364e3204fe1c0ac9af2.tar.xz
KVM: x86: Assume a 64-bit hypercall for guests with protected state
When processing a hypercall for a guest with protected state, currently SEV-ES guests, the guest CS segment register can't be checked to determine if the guest is in 64-bit mode. For an SEV-ES guest, it is expected that communication between the guest and the hypervisor is performed to shared memory using the GHCB. In order to use the GHCB, the guest must have been in long mode, otherwise writes by the guest to the GHCB would be encrypted and not be able to be comprehended by the hypervisor. Create a new helper function, is_64_bit_hypercall(), that assumes the guest is in 64-bit mode when the guest has protected state, and returns true, otherwise invoking is_64_bit_mode() to determine the mode. Update the hypercall related routines to use is_64_bit_hypercall() instead of is_64_bit_mode(). Add a WARN_ON_ONCE() to is_64_bit_mode() to catch occurences of calls to this helper function for a guest running with protected state. Fixes: f1c6366e3043 ("KVM: SVM: Add required changes to support intercepts under SEV-ES") Reported-by: Sean Christopherson <seanjc@google.com> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com> Message-Id: <e0b20c770c9d0d1403f23d83e785385104211f74.1621878537.git.thomas.lendacky@amd.com> Cc: stable@vger.kernel.org Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/sparc/Makefile')
0 files changed, 0 insertions, 0 deletions