[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <a38fed68-67bc-98ce-8e12-743342121ae3@oracle.com>
Date: Mon, 12 Jan 2026 01:17:53 -0500
From: Eugene Loh <eugene.loh@...cle.com>
To: jolsa@...nel.org
Cc: song@...nel.org, ast@...nel.org, rostedt@...dmis.org,
linux-kernel@...r.kernel.org, Kris Van Hees <kris.van.hees@...cle.com>
Subject: aarch64 missing from Revert "perf/x86: Always store regs->ip in
perf_callchain_kernel()"
Thanks for reverting that patch:
https://lore.kernel.org/r/20251104215405.168643-2-jolsa@kernel.org
https://github.com/torvalds/linux/commit/6d08340d1e354787d6c65a8c3cdd4d41ffb8a5ed
Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()"
This reverts commit 83f44ae.
But it seems to me that this issue is not specific to x86. For example,
here is aarch64, using a 6.18 kernel:
# bpftrace -e 'tracepoint:sched:sched_process_exec {
print(kstack()); }'
perf_trace_sched_process_exec+16
perf_trace_sched_process_exec+16
__traceiter_sched_process_exec+80
exec_binprm+908
bprm_execve.part.0+464
bprm_execve+68
do_execveat_common.isra.0+456
__arm64_sys_execve+76
invoke_syscall+112
el0_svc_common.constprop.0+264
do_el0_svc+36
el0_svc+56
el0t_64_sync_handler+184
el0t_64_sync+412
The leaf IP is repeated. Are corresponding changes needed for
processors other than just x86?
Powered by blists - more mailing lists