linux-kernel - Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

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: <20060915204812.GA6909@elte.hu>
Date:	Fri, 15 Sep 2006 22:48:13 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, karim@...rsys.com,
	Andrew Morton <akpm@...l.org>,
	Paul Mundt <lethal@...ux-sh.org>, Jes Sorensen <jes@....com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	Ingo Molnar <mingo@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Tom Zanussi <zanussi@...ibm.com>, ltt-dev@...fik.org,
	Michel Dagenais <michel.dagenais@...ymtl.ca>
Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108


* Roman Zippel <zippel@...ux-m68k.org> wrote:

> On Fri, 15 Sep 2006, Thomas Gleixner wrote:
> 
> > So this has to be changed. And requiring to recompile the kernel is the
> > wrong answer. Having some nifty tool, which allows you to define the set
> > of dynamic trace points or use a predefined one is the way to go.
> 
> Nobody is taking dynamic tracing away!
> You make it sound that tracing is only possible via dynamic traces.
> If I want to use static tracepoints, why shouldn't I?

because:

 - static tracepoints, once added, are very hard to remove - up until
   eternity. (On the other hand, markers for dynamic tracers are easily 
   removed, either via making the dynamic tracer smarter, or by 
   detaching the marker via the patch(1) method. In any case, if a 
   marker goes away then hell does not break loose in dynamic tracing 
   land - but it does in static tracing land.

 - the markers needed for dynamic tracing are different from the LTT
   static tracepoints.

 - a marker for dynamic tracing has lower performance impact than a 
   static tracepoint, on systems that are not being traced. (but which 
   have the tracing infrastructure enabled otherwise)

 - having static tracepoints dillutes the incentive for architectures to
   implement proper kprobes support.

> > > there are separate project teams is because managers in key 
> > > positions made the decision that they'd rather break from existing 
> > > projects which had had little success mainlining and instead use 
> > > their corporate bodyweight to pressure/seduce kernel developers 
> > > working for them into pushing their new great which-aboslutely- 
> > > has-nothing-to-do-with-this-ltt-crap-(no,no, we actually agree 
> > > with you kernel developers that this is crap, this is why we're 
> > > developing this new amazing thing). That's the truth plain and 
> > > simple.
> >
> > Stop whining!
> 
> So we're back to personal attacks now. :-(

hm, so you dont consider the above paragraph a whine. How would you 
characterize it then? A measured, balanced, on-topic technical comment? 
I'm truly curious.

	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/