From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
srutherford@google.com, joro@8bytes.org, brijesh.singh@amd.com,
thomas.lendacky@amd.com, venu.busireddy@oracle.com,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@suse.de>,
x86@kernel.org, Ashish Kalra <ashish.kalra@amd.com>
Subject: Re: [PATCH 0/3] KVM: x86: guest interface for SEV live migration
Date: Tue, 20 Apr 2021 20:27:50 +0200 [thread overview]
Message-ID: <2b1f1764-bcb0-096a-8d44-aee94f2c85f3@redhat.com> (raw)
In-Reply-To: <YH7wAh0t+eQ5n1M2@google.com>
On 20/04/21 17:15, Sean Christopherson wrote:
> On Tue, Apr 20, 2021, Paolo Bonzini wrote:
>> Do not return the SEV-ES bit from KVM_GET_SUPPORTED_CPUID unless
>> the corresponding module parameter is 1, and clear the memory encryption
>> leaf completely if SEV is disabled.
>
> Impeccable timing, I was planning on refreshing my SEV cleanup series[*] today.
> There's going to be an annoying conflict with the svm_set_cpu_caps() change
> (see below), any objecting to folding your unintentional feedback into my series?
That's fine of course.
>> diff --git a/arch/x86/kvm/cpuid.h b/arch/x86/kvm/cpuid.h
>> index 888e88b42e8d..e873a60a4830 100644
>> --- a/arch/x86/kvm/cpuid.h
>> +++ b/arch/x86/kvm/cpuid.h
>> @@ -99,6 +99,7 @@ static const struct cpuid_reg reverse_cpuid[] = {
>> [CPUID_7_EDX] = { 7, 0, CPUID_EDX},
>> [CPUID_7_1_EAX] = { 7, 1, CPUID_EAX},
>> [CPUID_12_EAX] = {0x00000012, 0, CPUID_EAX},
>> + [CPUID_8000_001F_EAX] = {0x8000001F, 0, CPUID_EAX},
>> };
>>
>> /*
>> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
>> index cd8c333ed2dc..acdb8457289e 100644
>> --- a/arch/x86/kvm/svm/svm.c
>> +++ b/arch/x86/kvm/svm/svm.c
>> @@ -923,6 +923,13 @@ static __init void svm_set_cpu_caps(void)
>> if (boot_cpu_has(X86_FEATURE_LS_CFG_SSBD) ||
>> boot_cpu_has(X86_FEATURE_AMD_SSBD))
>> kvm_cpu_cap_set(X86_FEATURE_VIRT_SSBD);
>> +
>> + /* CPUID 0x8000001F */
>> + if (sev) {
>> + kvm_cpu_cap_set(X86_FEATURE_SEV);
>> + if (sev_es)
>> + kvm_cpu_cap_set(X86_FEATURE_SEV_ES);
>
> Gah, I completely spaced on the module params in my series, which is more
> problematic than normal because it also moves "sev" and "sev_es" to sev.c. The
> easy solution is to add sev_set_cpu_caps().
Sounds good.
Paolo
next prev parent reply other threads:[~2021-04-20 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 11:20 Paolo Bonzini
2021-04-20 15:15 ` Sean Christopherson
2021-04-20 18:27 ` Paolo Bonzini [this message]
2021-04-20 17:31 ` Sean Christopherson
2021-04-20 18:11 ` Ashish Kalra
2021-04-20 18:40 ` Sean Christopherson
2021-04-20 18:58 ` Sean Christopherson
2021-04-20 18:39 ` Paolo Bonzini
2021-04-20 19:02 ` Sean Christopherson
2021-04-20 20:16 ` Sean Christopherson
2021-04-20 20:58 ` Paolo Bonzini
2021-04-20 22:49 ` Sean Christopherson
2021-04-20 23:20 ` Sean Christopherson
2021-04-21 12:03 ` 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=2b1f1764-bcb0-096a-8d44-aee94f2c85f3@redhat.com \
--to=pbonzini@redhat.com \
--cc=ashish.kalra@amd.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=srutherford@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=venu.busireddy@oracle.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®