[Ksummit-2008-discuss] Potential Systemtap topics for the Kernel Summit

[H. Peter Anvin]

Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Stephen Hemminger wrote:
>> On a related topic. Why not figure out a way to embed the tapsets
>> into the kernel source (a.l.a Docbook)?
> 
> Sure, why not.  The only problem is to come up with a notation which
> isn't too invasive.  Frank's example showed one problem tapsets are
> supposed to solve: make parameters available under a name which doesn't
> change.  Another goal for them is to make commonly used expressions
> derived from the state when entering the function available (e.g., inode
> belonging to a file descriptor).
> 
> This kind of information might need a single line for each convenience
> variable defined in the tapset.  So, it should be manageable.
> 

They wouldn't even have to be embedded in the C code directly (unless 
that makes them easier to write by being in situ), but even just having 
them as separate files in the kernel tarball should make keeping them in 
sync easier.

	-hpa