[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060917192359.GA24016@elte.hu>
Date: Sun, 17 Sep 2006 21:23:59 +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:
> > [...] I think Ingo said that some "static tracepoints" (eg.
> > annotation) could be acceptable.
>
> No, he made it rather clear, that as far as possible he only wants
> dynamic annotations (e.g. via function attributes).
what you say is totally and utterly nonsensical misrepresentation of
what i have said. I always said: i support in-source annotations too (I
even suggested APIs how to do them), as long as they are not a total
_guaranteed_ set destined for static tracers, i.e. as long as they are
there for the purpose of dynamic tracers. I dont _care_ about static
annotations as long as they are there for dynamic tracers, because they
can be moved into scripts if they cause problems. But static annotations
for static tracers are much, much harder to remove. Please go on and
read my "tracepoint maintainance models" email:
Message-ID: <20060917143623.GB15534@...e.hu>
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