From: Tom Lendacky <thomas.lendacky@amd.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Brijesh Singh <brijesh.singh@amd.com>,
Ashish Kalra <Ashish.Kalra@amd.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
kvm list <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: x86: Assume a 64-bit hypercall for guests with protected state
Date: Tue, 26 Oct 2021 13:03:00 -0500 [thread overview]
Message-ID: <e45669fa-372f-a29d-d9c9-b4747e56b97c@amd.com> (raw)
In-Reply-To: <3b8953c9-0611-27da-f955-c79a6fcef9ce@amd.com>
On 10/1/21 12:06 PM, Tom Lendacky wrote:
> On 5/25/21 1:25 AM, Vitaly Kuznetsov wrote:
>> Tom Lendacky <thomas.lendacky@amd.com> writes:
>>
>>> 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>
>>> ---
>>>
>>> Changes since v1:
>>> - Create a new helper routine, is_64_bit_hypercall(), and use it in place
>>> of is_64_bit_mode() in hypercall related areas.
>>> - Add a WARN_ON_ONCE() to is_64_bit_mode() to issue a warning if invoked
>>> for a guest with protected state.
>>> ---
>>> arch/x86/kvm/hyperv.c | 4 ++--
>>> arch/x86/kvm/x86.c | 2 +-
>>> arch/x86/kvm/x86.h | 12 ++++++++++++
>>> arch/x86/kvm/xen.c | 2 +-
>>> 4 files changed, 16 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
>>> index f98370a39936..1cdf2b213f41 100644
>>> --- a/arch/x86/kvm/hyperv.c
>>> +++ b/arch/x86/kvm/hyperv.c
>>> @@ -1818,7 +1818,7 @@ static void kvm_hv_hypercall_set_result(struct
>>> kvm_vcpu *vcpu, u64 result)
>>> {
>>> bool longmode;
>>> - longmode = is_64_bit_mode(vcpu);
>>> + longmode = is_64_bit_hypercall(vcpu);
>>> if (longmode)
>>> kvm_rax_write(vcpu, result);
>>> else {
>>> @@ -1895,7 +1895,7 @@ int kvm_hv_hypercall(struct kvm_vcpu *vcpu)
>>> }
>>> #ifdef CONFIG_X86_64
>>> - if (is_64_bit_mode(vcpu)) {
>>> + if (is_64_bit_hypercall(vcpu)) {
>>> param = kvm_rcx_read(vcpu);
>>> ingpa = kvm_rdx_read(vcpu);
>>> outgpa = kvm_r8_read(vcpu);
>>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>>> index 9b6bca616929..dc72f0a1609a 100644
>>> --- a/arch/x86/kvm/x86.c
>>> +++ b/arch/x86/kvm/x86.c
>>> @@ -8403,7 +8403,7 @@ int kvm_emulate_hypercall(struct kvm_vcpu *vcpu)
>>> trace_kvm_hypercall(nr, a0, a1, a2, a3);
>>> - op_64_bit = is_64_bit_mode(vcpu);
>>> + op_64_bit = is_64_bit_hypercall(vcpu);
>>> if (!op_64_bit) {
>>> nr &= 0xFFFFFFFF;
>>> a0 &= 0xFFFFFFFF;
>>> diff --git a/arch/x86/kvm/x86.h b/arch/x86/kvm/x86.h
>>> index 521f74e5bbf2..3102caf689d2 100644
>>> --- a/arch/x86/kvm/x86.h
>>> +++ b/arch/x86/kvm/x86.h
>>> @@ -151,12 +151,24 @@ static inline bool is_64_bit_mode(struct kvm_vcpu
>>> *vcpu)
>>> {
>>> int cs_db, cs_l;
>>> + WARN_ON_ONCE(vcpu->arch.guest_state_protected);
>>> +
>>> if (!is_long_mode(vcpu))
>>> return false;
>>> static_call(kvm_x86_get_cs_db_l_bits)(vcpu, &cs_db, &cs_l);
>>> return cs_l;
>>> }
>>> +static inline bool is_64_bit_hypercall(struct kvm_vcpu *vcpu)
>>> +{
>>> + /*
>>> + * If running with protected guest state, the CS register is not
>>> + * accessible. The hypercall register values will have had to been
>>> + * provided in 64-bit mode, so assume the guest is in 64-bit.
>>> + */
>>> + return vcpu->arch.guest_state_protected || is_64_bit_mode(vcpu);
>>> +}
>>> +
>>> static inline bool is_la57_mode(struct kvm_vcpu *vcpu)
>>> {
>>> #ifdef CONFIG_X86_64
>>> diff --git a/arch/x86/kvm/xen.c b/arch/x86/kvm/xen.c
>>> index ae17250e1efe..c58f6369e668 100644
>>> --- a/arch/x86/kvm/xen.c
>>> +++ b/arch/x86/kvm/xen.c
>>> @@ -680,7 +680,7 @@ int kvm_xen_hypercall(struct kvm_vcpu *vcpu)
>>> kvm_hv_hypercall_enabled(vcpu))
>>> return kvm_hv_hypercall(vcpu);
>>> - longmode = is_64_bit_mode(vcpu);
>>> + longmode = is_64_bit_hypercall(vcpu);
>>> if (!longmode) {
>>> params[0] = (u32)kvm_rbx_read(vcpu);
>>> params[1] = (u32)kvm_rcx_read(vcpu);
>>
>> Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>>
>> Thanks!
>
> Paolo,
>
> This got lost in my stack of work... any comments?
>
> Thanks,
> Tom
Ping
Thanks,
Tom
>
>>
next prev parent reply other threads:[~2021-10-26 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 17:48 Tom Lendacky
2021-05-25 6:25 ` Vitaly Kuznetsov
2021-10-01 17:06 ` Tom Lendacky
2021-10-26 18:03 ` Tom Lendacky [this message]
2021-11-11 20:46 ` Tom Lendacky
2021-11-16 15:05 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e45669fa-372f-a29d-d9c9-b4747e56b97c@amd.com \
--to=thomas.lendacky@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®