lkml.org 
[lkml]   [2008]   [Oct]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] ftrace: ftrace dump on oops control

* Steven Rostedt <rostedt@goodmis.org> wrote:

> [
> Changes since v1:
>
> Replaced /** with /* as Randy explained that kernel-doc does
> not yet handle variables.
> ]
>
> Currently, ftrace is set up to dump its contents to the console if the
> kernel panics or oops. This can be annoying if you have trace data in
> the buffers and you experience an oops, but the trace data is old or
> static.
>
> Usually when you want ftrace to dump its contents is when you are debugging
> your system and you have set up ftrace to trace the events leading to
> an oops.
>
> This patch adds a control variable called "ftrace_dump_on_oops" that will
> enable the ftrace dump to console on oops. This variable is default off
> but a developer can enable it either through the kernel command line
> by adding "ftrace_dump_on_oops" or at run time by setting (or disabling)
> /proc/sys/kernel/ftrace_dump_on_oops.
>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
> ---
> include/linux/ftrace.h | 2 ++
> kernel/sysctl.c | 10 ++++++++++
> kernel/trace/trace.c | 29 ++++++++++++++++++++++++++---
> 3 files changed, 38 insertions(+), 3 deletions(-)

applied to tip/tracing/ftrace, thanks Steve!

Ingo


\
 
 \ /
  Last update: 2008-10-27 15:07    [W:0.061 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site