aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorAdrian Hunter <[email protected]>2015-08-19 17:29:20 +0300
committerArnaldo Carvalho de Melo <[email protected]>2015-08-19 14:15:25 -0300
commit5cb73340d92a716fd2776700742c3558206ae298 (patch)
treed0a04e74f6ae50c222f84bfd87aaa45d2391643e /tools/perf/scripts/python/check-perf-trace.py
parent0d7e7acc47133e82911e24758178815cfee309e9 (diff)
perf tools: Make fork event processing more resilient
When processing a fork event, the tools lookup the parent thread by its tid. In a couple of cases, it is possible for that thread to have the wrong pid. That can happen if the data is being processed out of order, or if the (fork) event that would have removed the erroneous thread was lost. Assume the latter case, print a dump message, remove the erroneous thread, create a new one with the correct pid, and keep going. Reported-by: Arnaldo Carvalho de Melo <[email protected]> Signed-off-by: Adrian Hunter <[email protected]> Tested-by: Jiri Olsa <[email protected]> Cc: Linus Torvalds <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions