[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060915104955.ad6c3622.akpm@osdl.org>
Date: Fri, 15 Sep 2006 10:49:55 -0700
From: Andrew Morton <akpm@...l.org>
To: karim@...rsys.com
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Roman Zippel <zippel@...ux-m68k.org>,
Tim Bird <tim.bird@...sony.com>, Ingo Molnar <mingo@...e.hu>,
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>,
Thomas Gleixner <tglx@...utronix.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
On Fri, 15 Sep 2006 10:57:29 -0400
Karim Yaghmour <karim@...rsys.com> wrote:
> But I submit to you that both explanations
> actually highlight the argument I was making earlier with regards to
> dynamic tracing (and gdb info in this case) actually require a non-
> expert to chase kernel versions and create appropriate appropriate
> scripts/config-info for the post-insertion of instrumentation
> ...
Again, I don't see this as a huge problem. patch(1) is able to keep track
of specific places within source code even in the presence of quite violent
changes to that source code. There's no reason why systemtap support code
cannot do the same.
-
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