This is the mail archive of the systemtap@sources.redhat.com mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi - It seems to me that the embedded-C mechanism outlined yesterday would render moot this particular "what is a tapset" thread. A "tapset" need be nothing other than a set of systemtap script files. Each set of files would concern itself with some particular area of the kernel, defining probes, aliases, global variables, functions, with perhaps a smattering of embedded C. If it turned out that some kernel developer were interested in statically inserting instrumentation related C code right into their area, they could do so at will. If not reachable with the ordinary script-level probe constructs, then embedded C code in a matching "tapset" could be written, fully specialized to that kernel-side code's interface. Therefore, for this interface, no standard API is necessary at all. - FChE
Attachment:
pgp00000.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |