diff options
| author |   Naveen N Rao <naveen@kernel.org> | 2024-10-30 12:38:36 +0530 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2024-10-31 11:00:52 +1100 |
| commit | 161d62c2b067c4071cb515efe16475171e1c051e (patch) | |
| tree | 1ecfeac892d484f8227bcd54420800f32f2b5bec /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | powerpc/kprobes: Use ftrace to determine if a probe is at function entry (diff) | |
| download | wireguard-linux-161d62c2b067c4071cb515efe16475171e1c051e.tar.xz wireguard-linux-161d62c2b067c4071cb515efe16475171e1c051e.zip | |
powerpc64/ftrace: Nop out additional 'std' instruction emitted by gcc v5.x
Gcc v5.x emits a 3-instruction sequence for -mprofile-kernel:
mflr r0
std r0, 16(r1)
bl _mcount
Gcc v6.x moved to a simpler 2-instruction sequence by removing the 'std'
instruction. The store saved the return address in the LR save area in
the caller stack frame for stack unwinding. However, with dynamic
ftrace, we no longer have a call to _mcount on kernel boot when ftrace
is not enabled. When ftrace is enabled, that store is performed within
ftrace_caller(). As such, the additional 'std' instruction is redundant.
Nop it out on kernel boot.
With this change, we now use the same 2-instruction profiling sequence
with both -mprofile-kernel, as well as -fpatchable-function-entry on
64-bit powerpc.
Signed-off-by: Naveen N Rao <naveen@kernel.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://patch.msgid.link/20241030070850.1361304-4-hbathini@linux.ibm.com
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions