linux-kernel - Re: tracepoint maintainance models

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]

Date:	Mon, 18 Sep 2006 06:09:47 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Karim Yaghmour <karim@...rsys.com>
Cc:	Nicholas Miell <nmiell@...cast.net>,
	Paul Mundt <lethal@...ux-sh.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>, Jes Sorensen <jes@....com>,
	Andrew Morton <akpm@...l.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	Tom Zanussi <zanussi@...ibm.com>,
	Richard J Moore <richardj_moore@...ibm.com>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	Michel Dagenais <michel.dagenais@...ymtl.ca>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Christoph Hellwig <hch@...radead.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	William Cohen <wcohen@...hat.com>,
	"Martin J. Bligh" <mbligh@...igh.org>
Subject: Re: tracepoint maintainance models


* Karim Yaghmour <karim@...rsys.com> wrote:

> Ingo Molnar wrote:
> > Amazing! So the trace data provided by those removed static markups 
> > (which were moved into dynamic scripts and are thus still fully 
> > available to dynamic tracers) are still available to LTT users? How is 
> > that possible, via quantum tunneling perhaps? ;-)

> Previously alluded to script can easily be made to read mainlined 
> dynamic scripts and generate alternate build files for the designate 
> source. Let me know if I need to expand on this.

That suggestion is so funny to me that i'll let it stand here in its 
absurdity :) Did i get it right, you are suggesting for LTT to build a 
full SystemTap interpreter, an script-to-C compiler, an embedded-C 
script interpreter, just to be able to build-time generate the SystemTap 
scripts back into the source code? Dont you realize that you've just 
invented SystemTap, sans the ability to remove inactive code? ;)

I know a much easier method: a "static tracer" can do all of that (and 
more), if you rename "SystemTap" to "static tracer" ;-)

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