From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
thomas.lendacky@amd.com, dgilbert@redhat.com
Subject: Re: [PATCH] KVM: x86: advertise absence of X86_BUG_NULL_SEG via CPUID
Date: Fri, 22 Oct 2021 10:27:34 +0200 [thread overview]
Message-ID: <de8dbc64-ae2d-aa9f-a973-171feb5874d6@redhat.com> (raw)
In-Reply-To: <CALMp9eR3bt5P_+ZTJqcckL1pbZCyS6dCNK8o2OQR-atU_A_jtQ@mail.gmail.com>
On 21/10/21 23:36, Jim Mattson wrote:
> On Thu, Oct 21, 2021 at 2:20 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> Guests have X86_BUG_NULL_SEG if and only if the host have it. Use
>> the info from static_cpu_has_bug to form the 0x80000021 CPUID leaf that
>> was defined for Zen3. Userspace can then set the bit even on older
>> CPUs that do not have the bug, such as Zen2.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> arch/x86/kvm/cpuid.c | 17 ++++++++++++++++-
>> 1 file changed, 16 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
>> index 2d70edb0f323..b51398e1727b 100644
>> --- a/arch/x86/kvm/cpuid.c
>> +++ b/arch/x86/kvm/cpuid.c
>> @@ -902,7 +902,13 @@ static inline int __do_cpuid_func(struct kvm_cpuid_array *array, u32 function)
>> entry->edx = 0;
>> break;
>> case 0x80000000:
>> - entry->eax = min(entry->eax, 0x8000001f);
>> + entry->eax = min(entry->eax, 0x80000021);
>> + /*
>> + * X86_BUG_NULL_SEG is not reported in CPUID on Zen2; in
>> + * that case, provide the CPUID leaf ourselves.
>> + */
>
> I think this is backwards. !X86_BUG_NULL_SEG isn't reported in CPUID on Zen2.
Right I should use the name of the bit instead.
>> + if (!static_cpu_has_bug(X86_BUG_NULL_SEG))
>> + entry->eax = max(entry->eax, 0x80000021);
>> break;
>> case 0x80000001:
>> cpuid_entry_override(entry, CPUID_8000_0001_EDX);
>> @@ -973,6 +979,15 @@ static inline int __do_cpuid_func(struct kvm_cpuid_array *array, u32 function)
>> entry->ebx &= ~GENMASK(11, 6);
>> }
>> break;
>> + case 0x80000020:
>> + entry->eax = entry->ebx = entry->ecx = entry->edx = 0;
>> + break;
>> + case 0x80000021:
>> + entry->ebx = entry->ecx = entry->edx = 0;
>> + entry->eax &= BIT(6);
>
> While we're here, shouldn't bit 0 (Processor ignores nested data
> breakpoints) and bit 2 (LFENCE is always dispatch serializing) also
> match the hardware?
Yes, that makes sense. Just wanted to gauge whether anybody thought it
a really bad idea.
Paolo
>
>> + if (!static_cpu_has_bug(X86_BUG_NULL_SEG))
>> + entry->eax |= BIT(6);
>> + break;
>> /*Add support for Centaur's CPUID instruction*/
>> case 0xC0000000:
>> /*Just support up to 0xC0000004 now*/
>> --
>> 2.27.0
>>
>
prev parent reply other threads:[~2021-10-22 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 21:19 Paolo Bonzini
2021-10-21 21:36 ` Jim Mattson
2021-10-22 8:27 ` Paolo Bonzini [this message]
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=de8dbc64-ae2d-aa9f-a973-171feb5874d6@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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®