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: <20060917214000.GD2145@elte.hu>
Date:	Sun, 17 Sep 2006 23:40:00 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	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:

> > As an aside, there are quite a number of different types of tracing 
> > things (mostly static, compile out) in the kernel. Everything from 
> > blktrace to various userspace notifiers to lots of /proc/stuff could 
> > be considered a type of static event tracing. I don't know what my 
> > point is other than all these big, disjoint frameworks trying to be 
> > pushed into the kernel. Are there any plans for working some things 
> > together, or is that somebody else's problem?
> 
> All the controversy around static tracing in general and LTT in 
> specific has prevented this so far...

BLKTRACE is a special-purpose tracing facility limited to one subsystem 
and written and maintained by the /same/ person (Jens) who maintains 
that subsystem. He maintains the subsystem, the tracer and the userspace 
tool that extracts the tracer data.

LTT on the other hand is a static tracer that affects _all_ subsystems. 
That is a very different situation from a maintainance overhead POV, and 
i believe you must know that.

your suggestion that this controversy has prevented consolidation in 
this area is baseless and misleading, please correct or retract it.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ