From: Jiri Olsa <jolsa@kernel.org>
To: Song Liu <songliubraving@fb.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, Yonghong Song <yhs@fb.com>,
Andrii Nakryiko <andrii@kernel.org>
Subject: [RFC] Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()"
Date: Mon, 29 Sep 2025 14:51:58 +0200 [thread overview]
Message-ID: <20250929125158.2488188-1-jolsa@kernel.org> (raw)
This reverts commit 83f44ae0f8afcc9da659799db8693f74847e66b3.
hi,
non hw events store first stack trace entry twice:
bpf_prog_2beb79c650d605dd_rawtracepoint_sched_process_exec_1+324
bpf_prog_2beb79c650d605dd_rawtracepoint_sched_process_exec_1+324
bpf_trace_run3+138
bprm_execve+1191
do_execveat_common.isra.0+404
__x64_sys_execve+56
do_syscall_64+130
entry_SYSCALL_64_after_hwframe+118
I traced it to [1] from 2019, which stores regs->ip implicitly to fix
raw tracepoints stacktrace. Revert does not seem to break raw tp
stacktrace for me. Song, any idea? I know it's long time ;-)
thanks,
jirka
[1] 83f44ae0f8af ("perf/x86: Always store regs->ip in perf_callchain_kernel()")
---
arch/x86/events/core.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index 7610f26dfbd9..38f7102e2dac 100644
--- a/arch/x86/events/core.c
+++ b/arch/x86/events/core.c
@@ -2787,13 +2787,13 @@ perf_callchain_kernel(struct perf_callchain_entry_ctx *entry, struct pt_regs *re
return;
}
- if (perf_callchain_store(entry, regs->ip))
- return;
-
- if (perf_hw_regs(regs))
+ if (perf_hw_regs(regs)) {
+ if (perf_callchain_store(entry, regs->ip))
+ return;
unwind_start(&state, current, regs, NULL);
- else
+ } else {
unwind_start(&state, current, NULL, (void *)regs->sp);
+ }
for (; !unwind_done(&state); unwind_next_frame(&state)) {
addr = unwind_get_return_address(&state);
--
2.51.0
next reply other threads:[~2025-09-29 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 12:51 Jiri Olsa [this message]
2025-09-30 22:53 ` [RFC] Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()" Song Liu
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=20250929125158.2488188-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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