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: <450A3E8E.7090700@us.ibm.com>
Date:	Thu, 14 Sep 2006 22:47:58 -0700
From:	Vara Prasad <prasadav@...ibm.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
CC:	Ingo Molnar <mingo@...e.hu>, Roman Zippel <zippel@...ux-m68k.org>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...l.org>, Ingo Molnar <mingo@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tom Zanussi <zanussi@...ibm.com>, ltt-dev@...fik.org,
	Michel Dagenais <michel.dagenais@...ymtl.ca>,
	systemtap <systemtap@...rceware.org>
Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

Mathieu Desnoyers wrote:

>* Ingo Molnar (mingo@...e.hu) wrote:
>  
>
>>* Roman Zippel <zippel@...ux-m68k.org> wrote:
>>
>>    
>>
>>>>>>also, the other disadvantages i listed very much count too. Static 
>>>>>>tracepoints are fundamentally limited because:
>>>>>>
>>>>>>            
>>>>>>
>[...]
>  
>
>>Right now they are 
>>pretty heavy cons as far as LTT goes, so obviously they have a primary 
>>impact on the topic at hand (whic is whether to merge LTT or not).
>>
>>    
>>
>
>Ingo, why are you arguing about static instrumentation when I don't submit any
>static instrumentation in my patch ? You can argue about static VS dynamic
>instrumentation all you want, but please don't apply this debate to a dicision
>about including or not a core tracing infrastructure that has nothing to do
>with the way instrumentation or probes are inserted.
>
>Mathieu
>
>
>  
>
I think Ingo is right in saying what we really need first is a generic 
mechanism in how to specify static markers in the kernel which can be 
used to put dynamic probes on demand or use as a real static function 
calls if one chooses. Once we agree on the marker mechanism dynamic 
tracing and static tracing can both co-exist happily.

Coming to your rest of the patches i really don't think we need whole 
lot more than the facilities we already got in the kernel. Frank has 
successfully demonstrated in OLS how one can use static markers by using 
only existing facilities in the kernel.

>OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
>Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 
>-
>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/
>
>  
>


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