]> www.infradead.org Git - users/jedix/linux-maple.git/commit
ftrace: Do not disabled function graph based on "disabled" field
authorSteven Rostedt <rostedt@goodmis.org>
Mon, 5 May 2025 21:21:11 +0000 (17:21 -0400)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Fri, 9 May 2025 19:19:10 +0000 (15:19 -0400)
commitf62e3de375150210335a063605ce0dd6a6746b78
tree0e87a1091a81a6e8632ecc29124483d530de8de3
parenta9839d204896c59b0e2ae08e571515b1cf752bd1
ftrace: Do not disabled function graph based on "disabled" field

The per CPU "disabled" value was the original way to disable tracing when
the tracing subsystem was first created. Today, the ring buffer
infrastructure has its own way to disable tracing. In fact, things have
changed so much since 2008 that many things ignore the disable flag.

Do not bother disabling the function graph tracer if the per CPU disabled
field is set. Just record as normal. If tracing is disabled in the ring
buffer it will not be recorded.

Also, when tracing is enabled again, it will not drop the return call of
the function.

Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: https://lore.kernel.org/20250505212235.715752008@goodmis.org
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace_functions_graph.c