diff options
author | 2024-09-09 14:42:50 -0700 | |
---|---|---|
committer | 2024-09-10 17:32:47 -0300 | |
commit | c8b9358778a82534251dc93ebc4601246d5ae04e (patch) | |
tree | 4c0e0c5e242c3ff9554bebb9b79e514d28a622ea /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | perf build: Remove unused feature test target (diff) | |
download | wireguard-linux-c8b9358778a82534251dc93ebc4601246d5ae04e.tar.xz wireguard-linux-c8b9358778a82534251dc93ebc4601246d5ae04e.zip |
perf annotate: Treat 'call' instruction as stack operation
I found some portion of mem-store events sampled on CALL instruction
which has no memory access. But it actually saves a return address
into stack. It should be considered as a stack operation like RET
instruction.
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20240909214251.3033827-1-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions