From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, X86 ML <x86@kernel.org>,
KVM <kvm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [PATCH] KVM: x86: Sort CPUID_8000_0021_EAX leaf bits properly
Date: Thu, 10 Apr 2025 14:46:39 -0700 [thread overview]
Message-ID: <Z_g8Py8Ow85Uj6RT@google.com> (raw)
In-Reply-To: <20250324160617.15379-1-bp@kernel.org>
On Mon, Mar 24, 2025, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
>
> WRMSR_XX_BASE_NS is bit 1 so put it there, add some new bits as
> comments only.
>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
> arch/x86/kvm/cpuid.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
> index 121edf1f2a79..e98ab18f784b 100644
> --- a/arch/x86/kvm/cpuid.c
> +++ b/arch/x86/kvm/cpuid.c
> @@ -1160,6 +1160,7 @@ void kvm_set_cpu_caps(void)
>
> kvm_cpu_cap_init(CPUID_8000_0021_EAX,
> F(NO_NESTED_DATA_BP),
> + F(WRMSR_XX_BASE_NS),
> /*
> * Synthesize "LFENCE is serializing" into the AMD-defined entry
> * in KVM's supported CPUID, i.e. if the feature is reported as
> @@ -1173,10 +1174,14 @@ void kvm_set_cpu_caps(void)
> SYNTHESIZED_F(LFENCE_RDTSC),
> /* SmmPgCfgLock */
> F(NULL_SEL_CLR_BASE),
> + /* UpperAddressIgnore */
> F(AUTOIBRS),
> EMULATED_F(NO_SMM_CTL_MSR),
> + /* FSRS */
> + /* FSRC */
I'm going to skip these, as they aren't yet publicly documented, and there are
patches proposed to add actual support. I wouldn't care all that much if these
didn't collide with Intel's version (the proposed patches name them AMD_FSxx).
https://lore.kernel.org/all/20241204134345.189041-2-davydov-max@yandex-team.ru
> /* PrefetchCtlMsr */
> - F(WRMSR_XX_BASE_NS),
> + /* GpOnUserCpuid */
> + /* EPSF */
FWIW, this one's also not in the APM (though the only APM I can find is a year old),
though it's in tools/x86/kcpuid.
> SYNTHESIZED_F(SBPB),
> SYNTHESIZED_F(IBPB_BRTYPE),
> SYNTHESIZED_F(SRSO_NO),
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-10 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 16:06 [PATCH] KVM: x86: Sort CPUID_8000_0021_EAX leaf bits properly Borislav Petkov
2025-04-10 21:46 ` Sean Christopherson [this message]
2025-04-11 9:45 ` Borislav Petkov
2025-04-25 22:09 ` Sean Christopherson
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=Z_g8Py8Ow85Uj6RT@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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