linux-kernel - Re: LTTng kernel integration roadmap, update

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081125085722.GJ20928@mit.edu>
Date:	Tue, 25 Nov 2008 03:57:22 -0500
From:	Theodore Tso <tytso@....EDU>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	ltt-dev@...ts.casi.polymtl.ca, Zhaolei <zhaolei@...fujitsu.com>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Ingo Molnar <mingo@...e.hu>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>, Sam Ravnborg <sam@...nborg.org>
Subject: Re: LTTng kernel integration roadmap, update

On Tue, Nov 25, 2008 at 03:24:14AM -0500, Christoph Hellwig wrote:
> On Mon, Nov 24, 2008 at 07:20:55AM -0500, Mathieu Desnoyers wrote:
> > The key idea behind this is to answer to Thomas Gleixner concerns, who
> > supports that a tracer should output data in text-format only so it can
> > be used with tools kernel developers have on their system, like "cat".
> 
> Last time I talked to Thomas and others it wasn't "text only" but text
> also in that you can just cat a debugfs file for simple tracing.  And I
> totally agree with that.  If you don't trace too much that's absolutely
> enough.  It's not enough for large traces on highly loaded enterprise
> or high-end embedded systems or things like flight recorder tracing, but
> for those requiring an external viewer is just fine.

I agree that we should have a text-based output format for kernel
hackers, as well as a binary high volume format.  I'd argue also that
since the text-based one would be used by kernel hackers, we don't
need to worry so much about keeping the format absolutely stable from
kernel version to kernel version (and it's not worth it to add version
tags to the text stream); people who care about a long-term, stable
interface should use the binary output format, IMHO.  

I'm not sure everyone will agree with me, but I think it helps to
simplify the effort behind the text-based output.

	  	     	 	       	       - Ted
--
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/