diff options
| author | Namhyung Kim <[email protected]> | 2022-10-20 10:26:39 -0700 |
|---|---|---|
| committer | Arnaldo Carvalho de Melo <[email protected]> | 2022-10-27 16:37:26 -0300 |
| commit | 6b7e02ab1262141cfebd05b68410fa297f557961 (patch) | |
| tree | 0b7996c3d629689f626b162e3f7d3f89cbf54229 /tools/perf/scripts/python/flamegraph.py | |
| parent | 4321ad4ee98b7325d6133e1d5b7fa25bcbdeb57e (diff) | |
perf test: Wait for a new thread when testing --per-thread record
Just running the target program is not enough to test multi-thread
target because it'd be racy perf vs target startup. I used the
initial delay but it cannot guarantee for perf to see the thread.
Instead, use wait_for_threads helper from shell/lib/waiting.sh to make
sure it starts the sibling thread first. Then perf record can use -p
option to profile the target process.
Reviewed-by: Adrian Hunter <[email protected]>
Signed-off-by: Namhyung Kim <[email protected]>
Acked-by: Ian Rogers <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: Jiri Olsa <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions