[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <y0md59revaw.fsf@ton.toronto.redhat.com>
Date: 19 Sep 2006 11:21:43 -0400
From: fche@...hat.com (Frank Ch. Eigler)
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Paul Mundt <lethal@...ux-sh.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Jes Sorensen <jes@....com>, Andrew Morton <akpm@...l.org>,
Tom Zanussi <zanussi@...ibm.com>,
Richard J Moore <richardj_moore@...ibm.com>,
Michel Dagenais <michel.dagenais@...ymtl.ca>,
Christoph Hellwig <hch@...radead.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
William Cohen <wcohen@...hat.com>,
"Martin J. Bligh" <mbligh@...igh.org>, Ingo Molnar <mingo@...e.hu>,
ltt-dev@...fik.org, systemtap@...rces.redhat.com
Subject: Re: [PATCH] Linux Kernel Markers
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.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
-
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