summaryrefslogtreecommitdiffstats
path: root/tapset/DEVGUIDE
diff options
context:
space:
mode:
authorJosh Stone <jistone@redhat.com>2009-04-14 12:34:12 -0700
committerJosh Stone <jistone@redhat.com>2009-04-14 12:34:12 -0700
commit1f65cc4ffd1bd362b10d7f07d1cb9c4e7de68027 (patch)
tree1948954f707ddcb3f879b5e7646533d8fea83199 /tapset/DEVGUIDE
parent891e4fb2d5bf81b540b66b126b2ba78d1b7f459b (diff)
downloadsystemtap-steved-1f65cc4ffd1bd362b10d7f07d1cb9c4e7de68027.tar.gz
systemtap-steved-1f65cc4ffd1bd362b10d7f07d1cb9c4e7de68027.tar.xz
systemtap-steved-1f65cc4ffd1bd362b10d7f07d1cb9c4e7de68027.zip
PR9953: split up the two process.* tapsets
The overlapping process.* tapsets are now separated. Those probe points documented in stapprobes(3stap) remain the same. Those that were formerly in stapprobes.process(3stap) have been renamed to kprocess, to reflect their kernel perspective on processes.
Diffstat (limited to 'tapset/DEVGUIDE')
-rw-r--r--tapset/DEVGUIDE6
1 files changed, 3 insertions, 3 deletions
diff --git a/tapset/DEVGUIDE b/tapset/DEVGUIDE
index e6bc3fb8..693521a8 100644
--- a/tapset/DEVGUIDE
+++ b/tapset/DEVGUIDE
@@ -59,8 +59,8 @@ For example, process execs can occur in either the do_execve() or the
compat_do_execve() functions. The following alias inserts probes at the
beginning of those functions:
-probe process.exec = kernel.function("do_execve"),
- kernel.function("compat_do_execve") {
+probe kprocess.exec = kernel.function("do_execve"),
+ kernel.function("compat_do_execve") {
< probe body >
}
@@ -87,7 +87,7 @@ process is retrieved by calling task_pid() and passing it the task_struct
pointer. In this case, the auxiliary function is an embedded C function
that's defined in the task tapset (task.stp).
-probe process.create = kernel.function("copy_process").return {
+probe kprocess.create = kernel.function("copy_process").return {
task = $return
new_pid = task_pid(task)
}