From b9c556e44326b40b2c927a0a5b5626332a8c9587 Mon Sep 17 00:00:00 2001 From: hunt Date: Tue, 22 Mar 2005 08:57:11 +0000 Subject: *** empty log message *** --- runtime/docs/html/dir_000004.html | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 runtime/docs/html/dir_000004.html (limited to 'runtime/docs/html/dir_000004.html') diff --git a/runtime/docs/html/dir_000004.html b/runtime/docs/html/dir_000004.html new file mode 100644 index 00000000..263e859d --- /dev/null +++ b/runtime/docs/html/dir_000004.html @@ -0,0 +1,30 @@ + + +SystemTap: probes/where_func/ Directory Reference + + + +
Main Page | Data Structures | Directories | File List | Data Fields | Globals | Related Pages
+
+probes / where_func
+

where_func Directory Reference

This is a silly little instrumentation routine to instrument functions entry by name. +More... + + + + + + +

Files

file  kprobe_where_funct.c [code]
file  README [code]
+

Detailed Description

+This is a silly little instrumentation routine to instrument functions entry by name. +

+It makes use of the SystemTap runtime libraries to break down the number of times the function by caller.

+It demonstrates kprobes, passing a module parameter, using the print buffer, and using _stp_print_symbol() to map the addresses back to locations in functions.

+By default it instruments schedule().

+The instrumentation module is built by having the kernel that is going to be instrumented currently on the machine and doing 

./build
+
The instrumentation is inserted as root with: 
/sbin/insmod kprobe_funct_where.ko funct_name=function_name
+
The instrumentation is removed as root with: 
/sbin/rmmod kprobe_funct_where
+
-Will Cohen
+Generated on Tue Mar 22 00:32:02 2005 for SystemTap. + -- cgit