[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111116143528.GB7323@somewhere.redhat.com>
Date: Wed, 16 Nov 2011 15:35:34 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Johannes Berg <johannes@...solutions.net>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] tracing: add trace console
On Wed, Nov 16, 2011 at 09:15:54AM -0500, Steven Rostedt wrote:
> [ Added Peter, Thomas and Andrew ]
>
> On Wed, 2011-11-16 at 11:18 +0100, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@...el.com>
> >
> > As described in the Kconfig entry, logging printk
> > output is useful to correlate (existing) printk
> > debugging with (existing) tracing. The easiest way
> > to achieve this is to register a console that just
> > calls trace_printk(), which this module does.
>
> I'm good with this. Anyone have any issues with it?
Correlating trace_printk with printk is a feature I've
often missed.
Acked-by: Frederic Weisbecker <fweisbec@...il.com>
Thanks.
--
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