From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Brian Gerst <brgerst@gmail.com>,
Juergen Gross <jgross@suse.com>, "H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
x86@kernel.org
Subject: Re: [tip: perf/core] uprobes/x86: Add support to emulate NOP5 instruction
Date: Wed, 9 Apr 2025 16:07:03 +0200 [thread overview]
Message-ID: <20250409140703.GB9833@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <174419899905.31282.16125441491898382603.tip-bot2@tip-bot2>
On Wed, Apr 09, 2025 at 11:43:19AM -0000, tip-bot2 for Jiri Olsa wrote:
> The following commit has been merged into the perf/core branch of tip:
>
> Commit-ID: 38440aebd4acc7bb3721eea77829bdb724d2551a
> Gitweb: https://git.kernel.org/tip/38440aebd4acc7bb3721eea77829bdb724d2551a
> Author: Jiri Olsa <jolsa@kernel.org>
> AuthorDate: Tue, 08 Apr 2025 23:13:09 +02:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Wed, 09 Apr 2025 12:35:17 +02:00
>
> uprobes/x86: Add support to emulate NOP5 instruction
>
> Adding support to emulate NOP5 as the original uprobe instruction.
>
> This change speeds up uprobe on top of NOP5 and is a preparation for
> usdt probe optimization, that will be done on top of NOP5 instruction.
>
> With this change the usdt probe on top of NOP5 won't take the performance
> hit compared to usdt probe on top of standard NOP instruction.
>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Brian Gerst <brgerst@gmail.com>
> Cc: Juergen Gross <jgross@suse.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Link: https://lore.kernel.org/r/20250408211310.51491-1-jolsa@kernel.org
> ---
> arch/x86/kernel/uprobes.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/x86/kernel/uprobes.c b/arch/x86/kernel/uprobes.c
> index 9194695..63cc68e 100644
> --- a/arch/x86/kernel/uprobes.c
> +++ b/arch/x86/kernel/uprobes.c
> @@ -608,6 +608,16 @@ static void riprel_post_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
> *sr = utask->autask.saved_scratch_register;
> }
> }
> +
> +static int is_nop5_insn(uprobe_opcode_t *insn)
> +{
> + return !memcmp(insn, x86_nops[5], 5);
> +}
> +
> +static bool emulate_nop5_insn(struct arch_uprobe *auprobe)
> +{
> + return is_nop5_insn((uprobe_opcode_t *) &auprobe->insn);
> +}
> #else /* 32-bit: */
> /*
> * No RIP-relative addressing on 32-bit
> @@ -621,6 +631,10 @@ static void riprel_pre_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
> static void riprel_post_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
> {
> }
> +static bool emulate_nop5_insn(struct arch_uprobe *auprobe)
> +{
> + return false;
> +}
> #endif /* CONFIG_X86_64 */
>
> struct uprobe_xol_ops {
> @@ -852,6 +866,8 @@ static int branch_setup_xol_ops(struct arch_uprobe *auprobe, struct insn *insn)
> break;
>
> case 0x0f:
> + if (emulate_nop5_insn(auprobe))
> + goto setup;
> if (insn->opcode.nbytes != 2)
> return -ENOSYS;
> /*
This is still very weird code. See the comment here:
https://lkml.kernel.org/r/20241213104536.GZ35539@noisy.programming.kicks-ass.net
prev parent reply other threads:[~2025-04-09 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 21:13 [PATCH 1/2] uprobes/x86: Add support to emulate nop5 instruction Jiri Olsa
2025-04-08 21:13 ` [PATCH 2/2] selftests/bpf: Add 5-byte nop uprobe trigger bench Jiri Olsa
2025-04-09 11:43 ` [tip: perf/core] selftests/bpf: Add 5-byte NOP " tip-bot2 for Jiri Olsa
2025-04-09 11:28 ` [PATCH 1/2] uprobes/x86: Add support to emulate nop5 instruction Oleg Nesterov
2025-04-09 11:49 ` Oleg Nesterov
2025-04-09 12:08 ` Jiri Olsa
2025-04-09 13:11 ` Oleg Nesterov
2025-04-09 16:37 ` Jiri Olsa
2025-04-09 17:58 ` Oleg Nesterov
2025-04-09 11:43 ` [tip: perf/core] uprobes/x86: Add support to emulate NOP5 instruction tip-bot2 for Jiri Olsa
2025-04-09 14:07 ` Peter Zijlstra [this message]
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=20250409140703.GB9833@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.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 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®