[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1250879439.2964.3.camel@localhost.localdomain>
Date: Fri, 21 Aug 2009 14:30:39 -0400
From: Steven Rostedt <srostedt@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-tip-commits@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Dave Jones <davej@...hat.com>,
Kyle McMartin <kyle@...artin.ca>, Greg KH <gregkh@...e.de>,
linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
catalin.marinas@....com, a.p.zijlstra@...llo.nl,
jens.axboe@...cle.com, fweisbec@...il.com, stable@...nel.org,
tglx@...utronix.de
Subject: Re: [tip:tracing/urgent] tracing: Fix too large stack usage in
do_one_initcall()
On Fri, 2009-08-21 at 11:13 -0700, Linus Torvalds wrote:
>
> On Fri, 21 Aug 2009, Andrew Morton wrote:
> >
> > Do we have a max-stack-depth tracer widget btw?
>
> Enable FTRACE and then STACK_TRACER. Then just do
>
> cat /sys/kernel/debug/tracing/stack_trace
>
> and you'll get this.
Just a nitpick, but you will want to also add "stacktrace" to the kernel
command line otherwise it is default off. If you forget to do that, you
can also enable it with /proc/sys/kernel/stack_tracer_enabled.
But if you forget what to do, the code will remind you:
[root@mxf ~]# cat /sys/kernel/debug/tracing/stack_trace
Depth Size Location (-1 entries)
----- ---- --------
#
# Stack tracer disabled
#
# To enable the stack tracer, either add 'stacktrace' to the
# kernel command line
# or 'echo 1 > /proc/sys/kernel/stack_tracer_enabled'
#
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists