diff options
| -rw-r--r-- | ChangeLog | 5 | ||||
| -rw-r--r-- | NEWS | 11 | ||||
| -rw-r--r-- | stapprobes.5.in | 14 |
3 files changed, 30 insertions, 0 deletions
@@ -1,3 +1,8 @@ +2008-02-18 Frank Ch. Eigler <fche@elastic.org> + + * NEWS, stapprobes.5.in: Document basic (non-symbolic prototype) + user-space probe points. + 2008-02-15 Frank Ch. Eigler <fche@elastic.org> * tapsets.cxx (function_name_last_match): New function. @@ -1,5 +1,16 @@ * What's new in version 0.6 / 0.6.1 +- Prototype support for user-space probing is showing some progress. + No symbolic notations are supported yet (so no probing by function names, + file names, process names, and no access to $context variables), but at + least it's something: + + probe process(PID).statement(ADDRESS).absolute { } + + This will set a uprobe on the given process-id and given virtual address. + The proble handler runs in kernel-space as usual, and can generally use + existing tapset functions. + - Crash utility can retrieve systemtap's relay buffer from a kernel dump image by using staplog which is a crash extension module. To use this feature, type commands as below from crash(8)'s command line: diff --git a/stapprobes.5.in b/stapprobes.5.in index 276358a0..642ed739 100644 --- a/stapprobes.5.in +++ b/stapprobes.5.in @@ -283,6 +283,20 @@ $var[N] indexes into an array. The index is given with a literal number. +.SS USER-SPACE +Early prototype support for user-space probing is available in the +form of a non-symbolic probe point: +.SAMPLE +process(PID).statement(ADDRESS).absolute +.ESAMPLE +is analogous to +.IR +kernel.statement(ADDRESS).absolute +in that both use raw (unverified) virtual addresses and provide +no $variables. The target PID parameter must identify a running +process, and ADDRESS should identify a valid instruction address. +All threads of that process will be probed. + .SS PROCFS These probe points allow procfs "files" in |