This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: question about module function probe
- From: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
- To: "Mao, Bibo" <bibo dot mao at intel dot com>, <systemtap at sources dot redhat dot com>
- Date: Thu, 2 Mar 2006 09:07:03 -0800
- Subject: RE: question about module function probe
bibo,mao wrote:
> Hi,
> I wrote one script to probe function in module, this script is like
> this: probe module("*").function("*interrupt*")
> {
> }
>
> And in the translated module source file, it includes some probepoints
> like this:
>
"kernel.function(\"wait_for_completion_interruptible@kernel/sched.c:3017
\")",
>
"kernel.function(\"wait_for_completion_interruptible_timeout@kernel/sche
d.c:3052\")",
> "kernel.function(\"interruptible_sleep_on@kernel/sched.c:3111\")",
>
"kernel.function(\"interruptible_sleep_on_timeout@kernel/sched.c:3126\")
",
> But these functions are not defined in the modules, maybe some modules
> call these function.
> And I think module functions should be defined and implemented in the
> modules.
I think that kernel.function(...) is treated internally as a syntactic
sugar for module("kernel").function(...), so module("*") would match the
kernel itself as well. Whether this is the desired behavior may be a
point of discussion...
Josh