From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@intel.com>,
Kim Phillips <kim.phillips@amd.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-coco@lists.linux.dev, x86@kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Nikunj A Dadhania <nikunj@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Michael Roth <michael.roth@amd.com>,
Borislav Petkov <borislav.petkov@amd.com>,
Naveen Rao <naveen.rao@amd.com>,
David Kaplan <david.kaplan@amd.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
stable@kernel.org
Subject: Re: [PATCH 1/3] cpu/bugs: Fix selecting Automatic IBRS using spectre_v2=eibrs
Date: Tue, 24 Feb 2026 21:40:28 +0000 [thread overview]
Message-ID: <E9013CF4-D30E-4366-A8C4-8C249ECF395C@alien8.de> (raw)
In-Reply-To: <6b3b0c86-99eb-406d-b88d-3d71613bef9e@intel.com>
On February 24, 2026 6:22:36 PM UTC, Dave Hansen <dave.hansen@intel.com> wrote:
>On 2/24/26 10:01, Kim Phillips wrote:
>> @@ -2136,7 +2136,8 @@ static void __init spectre_v2_select_mitigation(void)
>> if ((spectre_v2_cmd == SPECTRE_V2_CMD_EIBRS ||
>> spectre_v2_cmd == SPECTRE_V2_CMD_EIBRS_LFENCE ||
>> spectre_v2_cmd == SPECTRE_V2_CMD_EIBRS_RETPOLINE) &&
>> - !boot_cpu_has(X86_FEATURE_IBRS_ENHANCED)) {
>> + !(boot_cpu_has(X86_FEATURE_IBRS_ENHANCED) ||
>> + boot_cpu_has(X86_FEATURE_AUTOIBRS))) {
>> pr_err("EIBRS selected but CPU doesn't have Enhanced or Automatic IBRS. Switching to AUTO select\n");
>> spectre_v2_cmd = SPECTRE_V2_CMD_AUTO;
>> }
>
>Didn't we agree to just use the "Intel feature" name? See this existing
>code:
>
>> /*
>> * AMD's AutoIBRS is equivalent to Intel's eIBRS - use the Intel feature
>> * flag and protect from vendor-specific bugs via the whitelist.
>> *
>> * Don't use AutoIBRS when SNP is enabled because it degrades host
>> * userspace indirect branch performance.
>> */
>> if ((x86_arch_cap_msr & ARCH_CAP_IBRS_ALL) ||
>> (cpu_has(c, X86_FEATURE_AUTOIBRS) &&
>> !cpu_feature_enabled(X86_FEATURE_SEV_SNP))) {
>> setup_force_cpu_cap(X86_FEATURE_IBRS_ENHANCED);
>> if (!cpu_matches(cpu_vuln_whitelist, NO_EIBRS_PBRSB) &&
>> !(x86_arch_cap_msr & ARCH_CAP_PBRSB_NO))
>> setup_force_cpu_bug(X86_BUG_EIBRS_PBRSB);
>> }
>
>You're probably not seeing X86_FEATURE_IBRS_ENHANCED because it doesn't
>get forced under SNP.
Set the Intel flag somewhere in the SNP init path...?
--
Small device. Typos and formatting crap
next prev parent reply other threads:[~2026-02-24 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 18:01 [PATCH 0/3] KVM: SEV: Add support for BTB Isolation Kim Phillips
2026-02-24 18:01 ` [PATCH 1/3] cpu/bugs: Fix selecting Automatic IBRS using spectre_v2=eibrs Kim Phillips
2026-02-24 18:22 ` Dave Hansen
2026-02-24 18:29 ` Jim Mattson
2026-02-24 21:40 ` Borislav Petkov [this message]
2026-02-24 18:01 ` [PATCH 2/3] cpu/bugs: Allow spectre_v2=ibrs on x86 vendors other than Intel Kim Phillips
2026-02-24 18:01 ` [PATCH 3/3] KVM: SEV: Add support for SNP BTB Isolation Kim Phillips
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=E9013CF4-D30E-4366-A8C4-8C249ECF395C@alien8.de \
--to=bp@alien8.de \
--cc=borislav.petkov@amd.com \
--cc=dave.hansen@intel.com \
--cc=david.kaplan@amd.com \
--cc=kim.phillips@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=naveen.rao@amd.com \
--cc=nikunj@amd.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@kernel.org \
--cc=thomas.lendacky@amd.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®