aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorNaveen N Rao <naveen@kernel.org>2024-10-30 12:38:35 +0530
committerMichael Ellerman <mpe@ellerman.id.au>2024-10-31 11:00:52 +1100
commitbe87d713eaddf0421ccd61cc060c4c29bc36fc9b (patch)
tree7328fca22cf32ab040555d974968a79f6465f7d9 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentpowerpc/trace: Account for -fpatchable-function-entry support by toolchain (diff)
downloadwireguard-linux-be87d713eaddf0421ccd61cc060c4c29bc36fc9b.tar.xz
wireguard-linux-be87d713eaddf0421ccd61cc060c4c29bc36fc9b.zip
powerpc/kprobes: Use ftrace to determine if a probe is at function entry
Rather than hard-coding the offset into a function to be used to determine if a kprobe is at function entry, use ftrace_location() to determine the ftrace location within the function and categorize all instructions till that offset to be function entry. For functions that cannot be traced, we fall back to using a fixed offset of 8 (two instructions) to categorize a probe as being at function entry for 64-bit elfv2, unless we are using pcrel. Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> 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-3-hbathini@linux.ibm.com
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions