[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1321456652.4502.12.camel@jlt3.sipsolutions.net>
Date: Wed, 16 Nov 2011 16:17:32 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Christoph Hellwig <hch@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] tracing: add trace console
On Wed, 2011-11-16 at 10:10 -0500, Christoph Hellwig wrote:
> On Wed, Nov 16, 2011 at 11:18:48AM +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'd much prefer if we could have it built in all the time, but had a
> way to enable it at runtime, just like all the "real" tracepoints.
That's possible, basically adding a tracepoints to printk -- that would
even catch everything and not require setting the console level (which
has its advantages too since other consoles might be slow).
It's a completely different thing though. I did it this way because it
was trivial to do out of tree for a quick test I was doing yesterday.
Doing it the other way is obviously more intrusive in core code.
johannes
--
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