systemtap/pcp integration

[Frank Ch. Eigler]

Hi, Nathan -

nathans wrote:

> [...]
> (OOC, what's {MODULE_NAME} in this context?)

It is usually a machine-generated unique identifier for the systemtap
script in question, such as "stap_deadbeefdeadbeefdeadbeef_2222".  It
is not generally predictable in advance.  (A user can override the
name, but that costs possible collisions.)


> [...] PMDA is written to be able to detect arrival/departure of new
> MMV files based on changes in a directory (and the location of that
> directory is parameterised via /etc/pcp.conf variables).  [...]

If we do end up sticking with this MMV approach, the PMDA would
probably need to use glob(3) or similar to search for
"/proc/systemtap/*/mmv" instead of "/proc/mmv/*".


> It also occurs to me that there's not really anything
> systemtap-specific about the kernel MMV instrumentation you've done,
> or is there?  [...]  It would be worth thinking about if the MMV
> bits in your script could become a more general kernel module for
> others to use too [...]

Yes, perhaps, though the path of code implementing a seemingly good
idea into the kernel is rarely smooth.  They generally dislike
infrastructure unless it's well-yearned-for.  So, if you wish to
pursue this goal, some serious selling on LKML will be needed.


- FChE