summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-02-08 23:18:02 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2025-02-08 23:18:02 +0300
commita0df483fe303e0c87a6d4a4f60213d5f8703c5ae (patch)
tree4c190192c36f143695e45fdf3643069e54d1b0b5 /tools/perf/scripts/python/task-analyzer.py
parenta5057ded6e882fc7a5f26de592259818ed07d397 (diff)
parentc8c9b1d2d5b4377c72a979f5a26e842a869aefc9 (diff)
downloadlinux-a0df483fe303e0c87a6d4a4f60213d5f8703c5ae.tar.xz
Merge tag 'ftrace-v6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull ftrace fix from Steven Rostedt: "Function graph fix of notrace functions. When the function graph tracer was restructured to use the global section of the meta data in the shadow stack, the bit logic was changed. There's a TRACE_GRAPH_NOTRACE_BIT that is the bit number in the mask that tells if the function graph tracer is currently in the "notrace" mode. The TRACE_GRAPH_NOTRACE is the mask with that bit set. But when the code we restructured, the TRACE_GRAPH_NOTRACE_BIT was used when it should have been the TRACE_GRAPH_NOTRACE mask. This made notrace not work properly" * tag 'ftrace-v6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace: fgraph: Fix set_graph_notrace with setting TRACE_GRAPH_NOTRACE_BIT
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions