redonkable
/
remarkable-linux
1
0
Fork 0
Code Releases Activity

tracing: keep the tracing buffer after self-test failure 

Instead of using ftrace_dump_on_oops, it's far more convenient
to have the trace leading up to a self-test failure available
in /debug/tracing/trace.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <1237694675-23509-1-git-send-email-fweisbec@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
wifi-calibration
Frederic Weisbecker 2009-03-22 15:13:07 +01:00 committed by Ingo Molnar
parent cf586b61f8
commit 0cf53ff62b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
kernel/trace/trace_selftest.c
View File

@ -299,7 +299,7 @@ trace_selftest_startup_function_graph(struct tracer *trace,
/* Have we just recovered from a hang? */
if (graph_hang_thresh > GRAPH_MAX_FUNC_TEST) {
trace->reset(tr);
tracing_selftest_disabled = true;
ret = -1;
goto out;
}