Re: [PATCH] markers-linker-generic

[Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>]

* Andrew Morton (akpm@linux-foundation.org) wrote:
> On Wed, 11 Apr 2007 13:51:11 -0400
> Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> 
> > > What's this marker stuff about?
> > > 
> > 
> > Hi Russel,
> > 
> > Here is an overview :
> 
> I am told that the systemtap developers plan to (or are) using this
> infrastructure.
> 

Quoting Frank Ch. Eigler, from the SystemTAP team :

"The LTTng user-space programs use it today.  Systemtap used to support
the earlier marker prototype and will be rapidly ported over to this
new API upon acceptance."


> If correct: what is their reason for preferring it over kprobes?
> 

I will let them answer on this one..

> 
> Secondly, the code in -mm has no actual backend for delivering anything to
> userspace or to anywhere else.  Why is this?

I wanted the community to come to an agreement regarding the
instrumentation mechanism before submitting a data transport backend.

> Which backends currently
> exist, and which ones are envisaged?  Is there a plan to merge any backend
> into the mainline kernel?
> 

Yes. The one I envisage to mainline is LTTng, available there :
http://ltt.polymtl.ca. It aims at providing the lowest system
disturbance and best performances possible, with reentrancy from almost
any kernel call site while keeping the task of adding new
instrumentation as easy as possible for the programmer. The current
patches are against 2.6.21-rc6-mm1. Is comes in small modules easy to
merge incrementally, which should make the whole process easier.

LKET, another tracer built on top of SystemTAP, can also be used to
extract the data to user space.

Mathieu


-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68