diff options
| author | Heiko Carstens <[email protected]> | 2023-10-30 15:50:47 +0000 |
|---|---|---|
| committer | Vasily Gorbik <[email protected]> | 2023-11-05 21:34:57 +0000 |
| commit | aa44433ac4ee2ae59b4b11e01eddb6241ae24ef5 (patch) | |
| tree | 75fec215f6dd53e54fa2116e6d0a9f3240b3b1fb /tools/testing/selftests/bpf/prog_tests/prog_array_init.c | |
| parent | s390/perf: implement perf_callchain_user() (diff) | |
| download | kernel-aa44433ac4ee2ae59b4b11e01eddb6241ae24ef5.tar.gz kernel-aa44433ac4ee2ae59b4b11e01eddb6241ae24ef5.zip | |
s390: add USER_STACKTRACE support
Use the perf_callchain_user() code as blueprint to also add support for
USER_STACKTRACE. To describe how to use this cite the commit message of the
LoongArch implementation which came with commit 4d7bf939df08 ("LoongArch:
Add USER_STACKTRACE support"), but replace -fno-omit-frame-pointer option
with the s390 specific -mbackchain option:
====================================================================== To
get the best stacktrace output, you can compile your userspace programs
with frame pointers (at least glibc + the app you are tracing).
1, export "CC = gcc -mbackchain";
2, compile your programs with "CC";
3, use uprobe to get stacktrace output.
...
echo 'p:malloc /usr/lib64/libc.so.6:0x0a4704 size=%r2:u64' > uprobe_events
echo 'p:free /usr/lib64/libc.so.6:0x0a4d50 ptr=%r2:u64' >> uprobe_events
echo 'comm == "demo"' > ./events/uprobes/malloc/filter
echo 'comm == "demo"' > ./events/uprobes/free/filter
echo 1 > ./options/userstacktrace
echo 1 > ./options/sym-userobj
...
======================================================================
Signed-off-by: Heiko Carstens <[email protected]>
Signed-off-by: Vasily Gorbik <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/prog_array_init.c')
0 files changed, 0 insertions, 0 deletions