Steven Rostedt faf6861ebd trace: print ftrace_dump at KERN_EMERG log level
Impact: fix to print out ftrace_dump when expected

I was debugging a hard race condition to only find out that
after I hit the race, my log level was not at level to show
KERN_INFO. The time it took to trigger the race was wasted because
I did not capture the trace.

Since ftrace_dump is only called from kernel oops (and only when
it is set in the kernel command line to do so), or when a
developer adds it to their own local tree, the log level of
the print should be at KERN_EMERG to make sure the print appears.

ftrace_dump is not called by a normal user setup, and will not
add extra unwanted print out to the console. There is no reason
it should be at KERN_INFO.

Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-01-21 15:21:30 +01:00
..
2009-01-12 16:39:58 -08:00
2009-01-08 08:31:10 -08:00
2009-01-15 16:39:37 -08:00
2008-10-16 11:21:30 -07:00
2008-07-28 14:37:38 +02:00
2007-07-16 09:05:50 -07:00
2009-01-06 15:59:27 -08:00
2008-12-10 08:01:54 -08:00
2008-08-13 12:55:10 +02:00
2008-10-20 15:43:10 +02:00
2009-01-08 08:31:02 -08:00
2009-01-08 08:31:12 -08:00
2008-09-02 19:21:40 -07:00
2009-01-06 11:07:15 +01:00
2009-01-15 21:07:57 +01:00
2008-11-05 10:30:14 +01:00
2007-07-16 09:05:50 -07:00
2008-02-06 10:41:02 -08:00
2008-10-16 11:21:47 -07:00
2008-10-16 11:21:31 -07:00