summaryrefslogtreecommitdiffstats
path: root/Documentation/trace
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2020-05-29 10:46:32 -0400
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2020-06-01 08:23:47 -0400
commitc200784a08d4ea82f82a30678955b7f2c7550af4 (patch)
tree519f863ac6d133ed1f651f0df597768b343cca37 /Documentation/trace
parent58f6e384480ec97b902e44399a44862907840ba9 (diff)
downloadlinux-c200784a08d4ea82f82a30678955b7f2c7550af4.tar.bz2
tracing: Add a trace print when traceoff_on_warning is triggered
When "traceoff_on_warning" is enabled and a warning happens, there can still be many trace events happening on other CPUs between the time the warning occurred and the last trace event on that same CPU. This can cause confusion in examining the trace, as it may not be obvious where the warning happened. By adding a trace print into the trace just before disabling tracing, it makes it obvious where the warning occurred, and the developer doesn't have to look at other means to see what CPU it occurred on. Cc: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'Documentation/trace')
0 files changed, 0 insertions, 0 deletions