[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1321453537.27735.0.camel@twins>
Date: Wed, 16 Nov 2011 15:25:37 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Johannes Berg <johannes@...solutions.net>,
LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] tracing: add trace console
On Wed, 2011-11-16 at 09:15 -0500, Steven Rostedt wrote:
> I'm good with this. Anyone have any issues with it?
>
> -- Steve
>
> >
> > Signed-off-by: Johannes Berg <johannes.berg@...el.com>
> > ---
> > kernel/trace/Kconfig | 13 ++++++++++
> > kernel/trace/Makefile | 2 +
> > kernel/trace/trace-console.c | 55 +++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 70 insertions(+)
> >
> > --- a/kernel/trace/Kconfig 2011-11-16 11:11:27.000000000 +0100
> > +++ b/kernel/trace/Kconfig 2011-11-16 11:11:35.000000000 +0100
> > @@ -368,6 +368,19 @@ config BLK_DEV_IO_TRACE
> >
> > If unsure, say N.
> >
> > +config TRACE_CONSOLE
> > + tristate "Support for a tracing console"
> > + help
> > + Say M (or Y if you must, but this is not recommended)
Why not?
> to be able
> > + to get a tracing console that puts every kernel message into the
> > + tracing infrastructure using trace_printk(). This is useful to
> > + correlate (existing) printk debugging with tracing. When using it
> > + remember to set the console level, e.g. with "dmesg -n8".
--
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