aboutsummaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2009-01-14 12:24:42 -0500
committerIngo Molnar <mingo@elte.hu>2009-01-21 15:21:30 +0100
commitfaf6861ebd776871e77b761c43ec045cd20b5716 (patch)
treec2e0a1294a18ea5c0ef359fde4b1d1df6a9f545c /Kbuild
parent551b4048b3d4acf15aff9fe4aed89b892c135b02 (diff)
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>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions