tapset/script information template

["Frank Ch. Eigler" <fche at redhat dot com>]

Hi -

In order to organize and collect the various application areas for
systemtap and its extension "tapsets", I propose filling in this
template, and committing it to a new directory within the CVS
repository.  

At the beginning, these tapset descriptions would just serve as
repository of ideas, to inform the implementors about requirements.
Over time, as the system starts to run, the description directories
can come to include real runnable code, test cases, documentation.


* Extension name: 
* Extension contact:
  (Give a name and contact for this tapset description.)

* Motivation:
  (Identify need: "known customer problem", "sysadmin curiosity",
   "design exploration", "matching dtrace/dprobes/... demo")

* Target software:
  (Identify the "kernel" and subsystems, or "user" and programs, or both)

* Interesting execution points:
  (Identify possible types of probe points within target software.
  Suggest probe point specifications to identify them in user scripts.) 

* Interesting values:
  (Identify data structures within target software that a user script
  may find interesting.  Identify those values that may be so simple and
  commonly used that the translator should map "macros" to them.)

* Conflicts, restrictions:
  (Describe

* Post-processing possibilities:

* List of associated files
  (This list is to document the illustrative files that are
   being kept

  FILE1
  - type of file (systemtap script?  j/kprobes source?  pseudocode?
                  dtrace script?  



- FChE

Attachment: pgp00000.pgp
Description: PGP signature