Messages in this thread | | | Date | Mon, 27 Oct 2008 15:03:58 +0100 | From | Ingo Molnar <> | Subject | Re: [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
| |