[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081023164032.GA19070@elte.hu>
Date: Thu, 23 Oct 2008 18:40:32 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Jan Kiszka <jan.kiszka@...mens.com>, linux-kernel@...r.kernel.org,
Frederic Weisbecker <fweisbec@...il.com>,
Abhishek Sagar <sagar.abhishek@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 08/13 v2] ftrace: do not trace init sections
* Steven Rostedt <rostedt@...dmis.org> wrote:
> > I don't know if this feature is already considered for / part of
> > mainline, but oops backtraces based on mcount instrumentation used
> > to be quite helpful for me to understand the wider context of
> > several faults. The more you have to mask out of this picture, the
> > harder it gets to match the trace to your model of the kernel
> > activities. At least you have to know more in advance about the
> > limitation of the tracer...
>
> The ftrace buffer can be dumped out on oops. I'm not sure if it is
> always on. If it is, I need to make it default off and add a command
> line and sysctl to turn it on. Otherwise, we will have people
> complaining about the extra output to the console on oops.
it dumps currently if a tracer is enabled. I saw it a couple of times
already during crashes.
Ingo
--
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