corrected: tapset/script information template

[Frank Ch. Eigler]

Hi -

wcohen wrote:

> [...]  I was thinking there are very specific places that one would
> want to start tracing and that it would be controlled by some
> probes, for example turning on the dynamic call graph when entering
> a "function of interest" and turning it off when exiting the same
> function.

By "turning it on/off" do you mean causing kernel- or hardware-level
configuration changes to occur during the execution of probe handlers?
That is, do you imagine the assignment of such variable to expand to
kernel API calls that turn on and off debug/counter hardware?


> I was thinking that instrumentation would be assisted by the debug
> hardware rather than the performance monitoring hardware. [...]  The
> debug also looks a bit easier to use: fewer bits to twiddle and
> easier to find the from/to address. [...]

Is there a standard kernel API for management/abstraction of x86 debug
hardware?  Can you outline the additional logic required to extract
this raw data and turn it into actual call/return trace events?


- 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/20050502/f1d212cc/attachment.sig>