This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH] Linux Kernel Markers
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Mathieu Desnoyers <mathieu dot desnoyers at polymtl dot ca>
- Cc: Paul Mundt <lethal at linux-sh dot org>, linux-kernel <linux-kernel at vger dot kernel dot org>, Jes Sorensen <jes at sgi dot com>, Andrew Morton <akpm at osdl dot org>, Tom Zanussi <zanussi at us dot ibm dot com>, Richard J Moore <richardj_moore at uk dot ibm dot com>, Michel Dagenais <michel dot dagenais at polymtl dot ca>, Christoph Hellwig <hch at infradead dot org>, Greg Kroah-Hartman <gregkh at suse dot de>, Thomas Gleixner <tglx at linutronix dot de>, William Cohen <wcohen at redhat dot com>, "Martin J. Bligh" <mbligh at mbligh dot org>, Ingo Molnar <mingo at elte dot hu>, ltt-dev at shafik dot org, systemtap at sources dot redhat dot com
- Date: 19 Sep 2006 11:21:43 -0400
- Subject: Re: [PATCH] Linux Kernel Markers
- References: <20060918234502.GA197@Krystal>
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> writes:
> [...] I take for agreed that both static and dynamic tracing are
> useful for different needs and that a full markup must support both
> and combinations, letting the user or the distribution choose.
Elaborating on Ingo's "one mechanism" comments, I believe a marker
widget needs to be generic at run time. We're not just looking for a
way of hiding direct calls to lttng in a marker macro. We're looking
for a way of marking spots & data in a uniform way, then later
(run-time) binding each of those markers to (tools such as) lttng
and/or systemtap.
- FChE