The CoreSight callchain test traces both userspace and kernel execution and checks the callchain across a syscall.
Add --kcore to perf record to save the running kernel image alongside the trace data so perf script can use it to decode the kernel trace.
Add a Fixes tag so the change can be backported to stable kernels and improve the test reliability.
Fixes: ca0e19074bd6 ("perf test: Add Arm CoreSight callchain test") Signed-off-by: Leo Yan leo.yan@arm.com --- tools/perf/tests/shell/coresight/callchain.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/tests/shell/coresight/callchain.sh b/tools/perf/tests/shell/coresight/callchain.sh index 13cca7dc1118..b69187f1a37f 100755 --- a/tools/perf/tests/shell/coresight/callchain.sh +++ b/tools/perf/tests/shell/coresight/callchain.sh @@ -43,7 +43,7 @@ record_trace()
mkfifo "$cf" "$af"
- perf record -o "$data" -e cs_etm// --per-thread -D -1 --control fifo:"$cf","$af" -- \ + perf record --kcore -o "$data" -e cs_etm// --per-thread -D -1 --control fifo:"$cf","$af" -- \ perf test --record-ctl fifo:"$cf","$af" -w callchain >/dev/null 2>&1 &&
# It is safe to use 'i3i' with a three-instruction interval, since the