Module Built Seperate from Kernel

Module Built Seperate from Kernel

[garogers01]

Is there a way to specify in the stap command file the location of a module
and it's files that are built independent of the kernel directory path?

For instance I have the following:

probe module("ocf").function("*") {
printf ("%s -> %s\n", thread_indent(1), probefunc())
}

probe module("icp_drv").function("*") {
printf ("%s -> %s\n", thread_indent(1), probefunc())
}

I get the following error:

semantic error: no match for probe point while resolving probe point
module("icp_drv").function("*")

Although the module is loaded, I don't see it or its' functions listed when
I use the -p2 option.  When I do a -p1 and look at the search trace, the
module build and file directory is not searched.  Is there a way to tell it
to search the module directory?

The module directory is in /root/driver/icp_drv 

Thanks,

Gerald Rogers
-- 
View this message in context: http://www.nabble.com/Module-Built-Seperate-from-Kernel-tp15048392p15048392.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.

Re: Module Built Seperate from Kernel

[Frank Ch. Eigler]

garogers01 <gerald.rogers@intel.com> writes:

> Is there a way to specify in the stap command file the location of a module
> and it's files that are built independent of the kernel directory path? [...]
>[...]
> Although the module is loaded, I don't see it or its' functions listed when
> I use the -p2 option.  [...]

That was a good guess.  What systemtap is really looking for however
is the actual .ko file on disk (and/or a separate stripped .ko.debug
file).

> The module directory is in /root/driver/icp_drv 

Until we get bug #2151 ("need method to specify debug search path")
fixed, would you consider putting in a symlink to this tree
under your /lib/modules/`uname -r`/ directory?

- FChE