diff options
author | Steven Rostedt <rostedt@goodmis.org> | 2008-07-30 22:36:46 -0400 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-10-14 10:35:26 +0200 |
commit | 3f5a54e371ca20b119b73704f6c01b71295c1714 (patch) | |
tree | 1453315564a19e967f11e612e264d4d2989afbe5 /include/linux/nodemask.h | |
parent | 2f2c99dba2398ef7d9c21f7c793180a50e68b1f0 (diff) |
ftrace: dump out ftrace buffers to console on panic
At OLS I had a lot of interest to be able to have the ftrace buffers
dumped on panic. Usually one would expect to uses kexec and examine
the buffers after a new kernel is loaded. But sometimes the resources
do not permit kdump and kexec, so having an option to still see the
sequence of events up to the crash is very advantageous.
This patch adds the option to have the ftrace buffers dumped to the
console in the latency_trace format on a panic. When the option is set,
the default entries per CPU buffer are lowered to 16384, since the writing
to the serial (if that is the console) may take an awful long time
otherwise.
[
Changes since -v1:
Got alpine to send correctly (as well as spell check working).
Removed config option.
Moved the static variables into ftrace_dump itself.
Gave printk a log level.
]
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'include/linux/nodemask.h')
0 files changed, 0 insertions, 0 deletions