Re: [PATCH v2] ftrace: ftrace dump on oops control

[Ingo Molnar]

* Steven Rostedt <rostedt@xxxxxxxxxxx> 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@xxxxxxxxxx>
> ---
>  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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/