diff options
| author | Namhyung Kim <[email protected]> | 2022-09-08 14:41:03 -0700 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2022-09-13 15:03:22 +0200 |
| commit | 16817ad7e8b31728b44ff9f17d8d894ed8a450d0 (patch) | |
| tree | 5d73d416cb0e2fe4b2f8f4c1a283ef3fff01a90b /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 3749d33e510c3dc695b3a5886b706310890d7ebd (diff) | |
perf/bpf: Always use perf callchains if exist
If the perf_event has PERF_SAMPLE_CALLCHAIN, BPF can use it for stack trace.
The problematic cases like PEBS and IBS already handled in the PMU driver and
they filled the callchain info in the sample data. For others, we can call
perf_callchain() before the BPF handler.
Signed-off-by: Namhyung Kim <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions