From: Jiri Olsa <olsajiri@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
David Laight <David.Laight@aculab.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org,
x86@kernel.org
Subject: Re: [RFC] x86/alternatives: Merge first and second step in text_poke_bp_batch
Date: Tue, 14 Jan 2025 15:31:14 +0100 [thread overview]
Message-ID: <Z4Z1MoJV0WW-vIHp@krava> (raw)
In-Reply-To: <20250114141723.GS5388@noisy.programming.kicks-ass.net>
On Tue, Jan 14, 2025 at 03:17:23PM +0100, Peter Zijlstra wrote:
> On Tue, Jan 14, 2025 at 03:02:37PM +0100, Jiri Olsa wrote:
> > hi,
> > while checking on similar code for uprobes I was wondering if we
> > can merge first 2 steps of instruction update in text_poke_bp_batch
> > function.
> >
> > Basically the first step now would be to write int3 byte together
> > with the rest of the bytes of the new instruction instead of doing
> > that separately. And the second step would be to overwrite int3
> > byte with first byte of the new instruction.
> >
> > Would that work or do I miss some x86 detail that could lead to crash?
>
> I *think* it will work on most modern systems, but I'm very sure I don't
> have all the details.
>
> IIRC this is the magic recipe blessed by both Intel and AMD, and
> if we're going to be changing this I would want both vendors to sign off
> on that.
ok
>
> > I tried to hack it together in attached patch and it speeds up a bit
> > text_poke_bp_batch as shown below.
>
> Why do we care about performance here?
just a benefit of doing that change.. but mainly I was just curious
on why those first steps are separated
thanks,
jirka
next prev parent reply other threads:[~2025-01-14 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 14:02 [RFC] x86/alternatives: Merge first and second step in text_poke_bp_batch Jiri Olsa
2025-01-14 14:17 ` Peter Zijlstra
2025-01-14 14:31 ` Jiri Olsa [this message]
2025-01-14 15:36 ` Steven Rostedt
2025-01-15 18:26 ` Jiri Olsa
2025-01-14 14:38 ` David Laight
2025-01-16 11:48 ` Jiri Olsa
2025-01-16 5:57 ` Masami Hiramatsu
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=Z4Z1MoJV0WW-vIHp@krava \
--to=olsajiri@gmail.com \
--cc=David.Laight@aculab.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.