This is the mail archive of the
mailing list for the systemtap project.
Re: [PATCH] Linux Kernel Markers
- From: Martin Bligh <mbligh at google dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: Ingo Molnar <mingo at elte dot hu>, Mathieu Desnoyers <mathieu dot desnoyers at polymtl dot ca>, Paul Mundt <lethal at linux-sh dot org>, linux-kernel <linux-kernel at vger dot kernel dot org>, Jes Sorensen <jes at sgi dot com>, Andrew Morton <akpm at osdl dot org>, Tom Zanussi <zanussi at us dot ibm dot com>, Richard J Moore <richardj_moore at uk dot ibm dot com>, Michel Dagenais <michel dot dagenais at polymtl dot ca>, Christoph Hellwig <hch at infradead dot org>, Greg Kroah-Hartman <gregkh at suse dot de>, Thomas Gleixner <tglx at linutronix dot de>, William Cohen <wcohen at redhat dot com>, ltt-dev at shafik dot org, systemtap at sources dot redhat dot com, Alan Cox <alan at lxorguk dot ukuu dot org dot uk>
- Date: Tue, 19 Sep 2006 09:52:55 -0700
- Subject: Re: [PATCH] Linux Kernel Markers
- Domainkey-signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:user-agent: x-accept-language:mime-version:to:cc:subject:references:in-reply-to: content-type:content-transfer-encoding; b=OGM6OmK0FjjcrvNtJ8/NPWCx6Wf7P51XQejTUZ7h9g5CNMKamvB/VePQBqe1mciTj sf+SXfvhuUMl8Vp6rr/Bg==
- References: <20060918234502.GA197@Krystal> <20060919081124.GA30394@elte.hu> <451008AC.email@example.com> <20060919154612.GU3951@redhat.com> <4510151B.firstname.lastname@example.org> <email@example.com>
Frank Ch. Eigler wrote:
Martin Bligh <firstname.lastname@example.org> writes:
[...] "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 [...]
Not quite. Systemtap does not look at sources, only object code and
its embedded debugging information. (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.
[...] 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?
Live code patching is theoretically useful for all kinds of things,
but I've never heard it described as relatively simple before! :-)
well, on a whole-function basis, it seems somewhat simpler.