[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060919170217.GA18646@redhat.com>
Date: Tue, 19 Sep 2006 13:02:17 -0400
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Martin Bligh <mbligh@...gle.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
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>, ltt-dev@...fik.org,
systemtap@...rces.redhat.com, Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Linux Kernel Markers
Hi -
On Tue, Sep 19, 2006 at 09:52:55AM -0700, Martin Bligh wrote:
> >[...] (How many distributions keep around compilable source
> >trees?)
>
> ???? Boggle. Any distro that cannot find the source code for it's kernel
> deserves a swift kick to the head, plus a red hot poker somewhere else.
My question is more whether they package up such a buildable
configured patched source tree (/usr/src/redhat/BUILD/* in RH-speak),
or just some extract like the .c/.h files.
> >>[...] It seems like all we'd need to do is "list all references to
> >>function, freeze kernel, update all references, continue", [...]
> >
> >One additional problem are external references made *by* the function.
> >Those too would all have to be relocated to the live data.
>
> Not sure what you mean ... could you give a quick example?
Think about stuff that any function does. It calls other functions,
and manipulates global data, which all show up as external references
in the object code. All those references would have to be patched to
refer to the live running copy of the original compilation unit.
- FChE
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists