From: Sean Christopherson <seanjc@google.com>
To: Yosry Ahmed <yosry.ahmed@linux.dev>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] x86/bugs: Use a static branch to guard IBPB on vCPU load
Date: Tue, 25 Feb 2025 14:40:24 -0800 [thread overview]
Message-ID: <Z75G2L6N1vR3DslT@google.com> (raw)
In-Reply-To: <59ea1984b2893be8a3a72855b022d16c67b857e9@linux.dev>
On Tue, Feb 25, 2025, Yosry Ahmed wrote:
> February 25, 2025 at 11:49 AM, "Sean Christopherson" <seanjc@google.com> wrote:
> >
> > On Wed, Feb 19, 2025, Yosry Ahmed wrote:
> > >
> > > Instead of using X86_FEATURE_USE_IBPB to guard the IBPB execution in the
> > > vCPU load path, introduce a static branch, similar to switch_mm_*_ibpb.
> > >
> > > This makes it obvious in spectre_v2_user_select_mitigation() what
> > > exactly is being toggled, instead of the unclear X86_FEATURE_USE_IBPB
> > > (which will be shortly removed). It also provides more fine-grained
> > > control, making it simpler to change/add paths that control the IBPB in
> > > the vCPU load path without affecting other IBPBs.
> > >
> > > Signed-off-by: Yosry Ahmed <yosry.ahmed@linux.dev>
> > >
> > > ---
> > >
> > > arch/x86/include/asm/nospec-branch.h | 2 ++
> > > arch/x86/kernel/cpu/bugs.c | 5 +++++
> > > arch/x86/kvm/svm/svm.c | 2 +-
> > > arch/x86/kvm/vmx/vmx.c | 2 +-
> > > 4 files changed, 9 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/x86/include/asm/nospec-branch.h b/arch/x86/include/asm/nospec-branch.h
> > > index 7cbb76a2434b9..a22836c5fb338 100644
> > > --- a/arch/x86/include/asm/nospec-branch.h
> > > +++ b/arch/x86/include/asm/nospec-branch.h
> > > @@ -552,6 +552,8 @@ DECLARE_STATIC_KEY_FALSE(switch_to_cond_stibp);
> > > DECLARE_STATIC_KEY_FALSE(switch_mm_cond_ibpb);
> > >
> DECLARE_STATIC_KEY_FALSE(switch_mm_always_ibpb);
> > >
> +DECLARE_STATIC_KEY_FALSE(vcpu_load_ibpb);
> > >
> >
> > How about ibpb_on_vcpu_load? To make it easy for readers to understand exactly
> > what the knob controls.
>
> I was trying to remain consistent with the existing static branches' names,
> but I am fine with ibpb_on_vcpu_load if others don't object.
I assumed as much :-) I'm ok with vcpu_load_ibpb if that's what others prefer.
next prev parent reply other threads:[~2025-02-25 22:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 22:08 [PATCH 0/6] IBPB cleanups and a fixup Yosry Ahmed
2025-02-19 22:08 ` [PATCH 1/6] x86/bugs: Move the X86_FEATURE_USE_IBPB check into callers Yosry Ahmed
2025-02-25 19:47 ` Sean Christopherson
2025-02-25 21:28 ` Yosry Ahmed
2025-02-19 22:08 ` [PATCH 2/6] x86/mm: Remove X86_FEATURE_USE_IBPB checks in cond_mitigation() Yosry Ahmed
2025-02-19 22:08 ` [PATCH 3/6] x86/bugs: Remove the X86_FEATURE_USE_IBPB check in ib_prctl_set() Yosry Ahmed
2025-02-19 22:08 ` [PATCH 4/6] x86/bugs: Use a static branch to guard IBPB on vCPU load Yosry Ahmed
2025-02-25 19:49 ` Sean Christopherson
2025-02-25 21:27 ` Yosry Ahmed
2025-02-25 22:40 ` Sean Christopherson [this message]
2025-02-26 2:49 ` Yosry Ahmed
2025-02-27 0:46 ` Sean Christopherson
2025-02-27 0:54 ` Yosry Ahmed
2025-02-19 22:08 ` [PATCH 5/6] KVM: nVMX: Always use IBPB to properly virtualize IBRS Yosry Ahmed
2025-02-19 23:09 ` Jim Mattson
2025-02-25 19:50 ` Sean Christopherson
2025-02-19 22:08 ` [PATCH 6/6] x86/bugs: Remove X86_FEATURE_USE_IBPB Yosry Ahmed
2025-02-20 19:04 ` [PATCH 0/6] IBPB cleanups and a fixup Josh Poimboeuf
2025-02-20 19:59 ` Yosry Ahmed
2025-02-20 20:47 ` Josh Poimboeuf
2025-02-20 21:50 ` Yosry Ahmed
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=Z75G2L6N1vR3DslT@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yosry.ahmed@linux.dev \
/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