For kernel modules OProfile just labels the samples for the kernel
module as /kmodule_name. When it comes to analysis this is not the right
name for the sample file. I have written a quick and dirty script to
find a matching module (assuming that the user installed a module in
the default location) and do the normal opreport or oprofpp analysis on
the module. Unfortunately due to the creation and removal of the
symbolic link the opreport_module script needs to be run as root. I
would like some feedback on this. There is probably better ways of doing
this than what is done in the script.
From: John Levon <levon@mo...> - 2005-07-18 18:54:16
On Mon, Jun 20, 2005 at 05:20:25PM -0400, William Cohen wrote:
> For kernel modules OProfile just labels the samples for the kernel
> module as /kmodule_name. When it comes to analysis this is not the right
I'd prefer to have code to "clean up" that name when we've found the
module via -p.
Get latest updates about Open Source Projects, Conferences and News.