[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z-W7mRAkMfFyJ6sE@gmail.com>
Date: Thu, 27 Mar 2025 21:56:57 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Eric Dumazet <edumazet@...gle.com>,
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>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Masami Hiramatsu <mhiramat@...nel.org>, x86@...nel.org,
bpf@...r.kernel.org, Eric Dumazet <eric.dumazet@...il.com>,
Greg Thelen <gthelen@...gle.com>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH] x86/alternatives: remove false sharing in
poke_int3_handler()
* Peter Zijlstra <peterz@...radead.org> wrote:
> On Tue, Mar 25, 2025 at 12:26:36PM +0100, Ingo Molnar wrote:
>
> > Yeah, so I do know what #BP is, but what the heck disambiguates the two
> > meanings of _bp and why do we have the above jungle of an inconsistent
> > namespace? :-)
> >
> > Picking _int3 would neatly solve all of that.
>
> Sure; the most obvious case where BP would make sense, the trap entry
> point, we already use int3 so yeah, make it int3 throughout.
Okay - I just sent out a series to do this. Found a few other things to
fix/improve along the way:
https://lore.kernel.org/r/20250327205355.378659-1-mingo@kernel.org
Thanks,
Ingo
Powered by blists - more mailing lists