[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250220204724.y3b6wx7y2ks3fuct@jpoimboe>
Date: Thu, 20 Feb 2025 12:47:24 -0800
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Yosry Ahmed <yosry.ahmed@...ux.dev>
Cc: x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] IBPB cleanups and a fixup
On Thu, Feb 20, 2025 at 07:59:54PM +0000, Yosry Ahmed wrote:
> > static inline void indirect_branch_prediction_barrier(void)
> > {
> > asm volatile(ALTERNATIVE("", "call write_ibpb", X86_FEATURE_IBPB)
> > : ASM_CALL_CONSTRAINT
> > : : "rax", "rcx", "rdx", "memory");
> > }
> >
> > I also renamed "entry_ibpb" -> "write_ibpb" since it's no longer just
> > for entry code.
>
> Do you want me to add this in this series or do you want to do it on top
> of it? If you have a patch lying around I can also include it as-is.
Your patches are already an improvement and can be taken as-is:
Acked-by: Josh Poimboeuf <jpoimboe@...nel.org>
I'll try to dust off my patches soon and rebase them on yours.
--
Josh
Powered by blists - more mailing lists