HI there,
I run into a problem where I think jdb module is not working
correctly with
opannotate. Here is my script to genereate the report files:
ln -s /lib/modules/`uname -r`/kernel ko.l
opreport -l -p ko.l/. > opreport.log
opreport -l > opreport-summary.log
opannotate --source -d /usr/src/linux -p ko.l/. >
opannotate.log
where in opreport.log, I saw a jdb function journal_dirty_data
which
uses 0.18% CPU, but in opannotate.log, function “journal_dirty_data”
is not listed at all. When I run the above script, I did get
the following
warnings:
warning: could not check that the binary file
/lib/modules/2.6.9-34.ELsmp/kernel/fs/jbd/jbd.ko has not been modified since
the profile was taken. Results may be inaccurate.
warning: /jbd could not be found.
I am not sure if that will explain what I missed here. BTW,
I started oprofile as following:
opcontrol --reset
opcontrol --start --vmlinux=/usr/src/linux/vmlinux
I am trying to understand the breakdown of time consumptions
within a function. If there is
other ways than opannotate to achieve this, Please let me
know. I really appreciate your
help.
Thanks,
--
John Liang