lkml.org 
[lkml]   [2006]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Linux Kernel Markers
Frank Ch. Eigler wrote:
> Martin Bligh <mbligh@google.com> 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.

M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-09-19 18:57    [from the cache]
©2003-2011 Jasper Spaans