C untapset

[Frank Ch. Eigler]

Hi -


Here is a scenario which, if we embrace, would have implications on
kprobes reentrancy as well as instrumentation reuse.

The idea is that, for whatever reason, there may be a batch of kprobes
or jprobes-based C code in existence or being written, which someone
may wish to reuse via systemtap.  Here's a limited way to do it:
within this C code, place a marker (or even just documentation) at
interesting control flow points, such as kprobes event handlers.

Then a systemtap user can place an ordinary, possibly kprobe-backed,
probe point into that lower level instrumentation.  The script code
would be able to pull out data from the variables visible to the
target C code.  They could even communicate by setting flags back and
forth.

This is in effect meta-instrumentation, and requires no changes in
current systemtap design.  On the other hand, it would require having
kprobes support full reentrancy (instead of blocking the nested trap).


- FChE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/systemtap/attachments/20050516/b4adcff8/attachment.sig>