summaryrefslogtreecommitdiffstats
path: root/drivers/net/tulip/dmfe.c
diff options
context:
space:
mode:
authorSteven Rostedt <rostedt@goodmis.org>2008-10-23 19:26:08 -0400
committerIngo Molnar <mingo@elte.hu>2008-10-27 15:03:15 +0100
commit944ac4259e39801c843a915c3da8194ac9af0440 (patch)
tree0b028e4dfa510e41e09a6497eab4ff9f16642245 /drivers/net/tulip/dmfe.c
parentf4a2a0d9a4226846693b5b4462d4350c1bfd58ea (diff)
downloadlinux-944ac4259e39801c843a915c3da8194ac9af0440.tar.bz2
ftrace: ftrace dump on oops control
Impact: add (default-off) dump-trace-on-oops flag 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. v2: Replaced /** with /* as Randy explained that kernel-doc does not yet handle variables. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/net/tulip/dmfe.c')
0 files changed, 0 insertions, 0 deletions