| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1321461902.4502.14.camel@jlt3.sipsolutions.net> Date: Wed, 16 Nov 2011 17:45:02 +0100 From: Johannes Berg <johannes@...solutions.net> To: Steven Rostedt <rostedt@...dmis.org> Cc: Christoph Hellwig <hch@...radead.org>, LKML <linux-kernel@...r.kernel.org>, Frederic Weisbecker <fweisbec@...il.com>, Ingo Molnar <mingo@...hat.com> Subject: Re: [PATCH] tracing: add trace console On Wed, 2011-11-16 at 11:41 -0500, Steven Rostedt wrote: > > 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. > > I'm not sure it would be too invasive. Think you could get something > working? I briefly looked at it just after writing the email, but quickly got lost in printk.c because of the multi-line handling it has. We could instead trace each call to printk(), so the multi-line stuff would end up in multiple events, but all of that code is too much vodoo for me :) 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