summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2026-07-31 13:25:45 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2026-07-31 13:25:45 -0700
commitce6ce829c80c692a8a9cb781d9156360c9ce6fa3 (patch)
treeee234c0e701a1ba843060b859c35dcdd032e93c8 /tools/perf/scripts/python/bin/stackcollapse-report
parent6269cc6f52c68f6f5474f86e94256c81d1ff24cb (diff)
parentfafb66e5903c2bcfc7b7e259042a8282f18a6faa (diff)
Merge tag 'trace-tools-v7.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull RTLA fix from Steven Rostedt: - Fix timerlat top actions triggering on signal Fix a bug in RTLA's timerlat top actions feature where on-threshold actions are triggered on any signal, regardless of whether a latency spike had actually occurred during the measurement. The return retval was checked for non-zero to do actions. But if a signal came in, it returns a negative and actions were being incorrectly triggered when they should not have been. * tag 'trace-tools-v7.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace: rtla/timerlat_top: Fix on-threshold actions firing on signal
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions