[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OFAEBEF5BB.1D00BC3E-ON802571EE.005B7AF8-802571EE.005BB61E@uk.ibm.com>
Date: Tue, 19 Sep 2006 17:41:43 +0100
From: Richard J Moore <richardj_moore@...ibm.com>
To: Martin Bligh <mbligh@...gle.com>
Cc: Andrew Morton <akpm@...l.org>, Alan Cox <alan@...rguk.ukuu.org.uk>,
"Frank Ch. Eigler" <fche@...hat.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
Christoph Hellwig <hch@...radead.org>,
Jes Sorensen <jes@....com>, Paul Mundt <lethal@...ux-sh.org>,
linux-kernel <linux-kernel@...r.kernel.org>, ltt-dev@...fik.org,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Michel Dagenais <michel.dagenais@...ymtl.ca>,
Ingo Molnar <mingo@...e.hu>, systemtap@...rces.redhat.com,
Thomas Gleixner <tglx@...utronix.de>,
William Cohen <wcohen@...hat.com>,
Tom Zanussi <zanussi@...ibm.com>
Subject: Re: [PATCH] Linux Kernel Markers
Martin Bligh <mbligh@...gle.com> wrote on 19/09/2006 17:04:43:
> Frank Ch. Eigler wrote:
> > Hi -
> >
> > On Tue, Sep 19, 2006 at 08:11:40AM -0700, Martin J. Bligh wrote:
> >
> >
> >>[...] Why don't we just copy the whole damned function somewhere
> >>else, and make an instrumented copy (as a kernel module)? Then
> >>reroute all the function calls through it [...]
> >
> >
> > Interesting idea. Are you imagining this instrumented copy being
> > built at kernel compile time (something like building a "-g -O0"
> > parallel)? Or compiled anew from original sources after deployment?
> > Or on-the-fly binary-level rewriting a la SPIN?
>
> "compiled anew from original sources after deployment" seems the most
> practical to do to me. From second hand info on using systemtap, you
> seem to need the same compiler and source tree to work from anyway, so
> this doesn't seem much of a burden.
>
If I'm not mistaken, this has been done before under the guise of dynamic
patch. Doesn't Solaris have the capability? I'm certain that some UNIXes do
as well as non-UNIX O/Ss.
Richard
-
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