Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I installed the oprofile 0.5.4 (BTW, oprofile 0.6.0 and 0.6.1 could not be
compiled at all, but after ignore the gui-related codes, I also managed to
compile and build them) on a RH-7.2 486 compatible computer. However, when I
tried to run "opcontrol --no-vmlinux --init", I got an error message like,
Cannot locate oprofile module
I then manually installed oprofile module with "insmod oprofile.o", but the
error message persists. I ignored this message which I should not:-), and
went ahead with collecting sampling data. But I got nothing under the
/var/lib/oprofile/samples directory (not unexpected!).
I was told that with the RTC mode, oprofile should be able to used on
unsupported architectures like accient 486 compatible, but it seems not easy
to do it. I read the news arhive, someone mentioned that oprofile only
supports SMP machines for RH 7.3 (or else 8.0, 9.0). How about the story
Anybody out there have a better experience please point me to the right
If you know some other tools, please share it with me. I have tried gprof,
qprof, gcov, etc. My goal is to profile multithreaded applications on a
RH-7.2 486 compatible uniprocessor machine.
Thanks and best,
From: Philippe Elie <phil.el@wa...> - 2003-09-20 01:51:49
Jianpeng Dong wrote:
> Hi all,
> I installed the oprofile 0.5.4 (BTW, oprofile 0.6.0 and 0.6.1 could not
> be compiled at all, but after ignore the gui-related codes, I also
> managed to compile and build them) on a RH-7.2 486 compatible computer.
> However, when I tried to run "opcontrol --no-vmlinux --init", I got an
> error message like,
> Cannot locate oprofile module
you must fix that first:
$ modprobe oprofile
should load correctly the driver, it is installed in
after a correct load of the driver you must get:
$ grep /proc/devices oprof
$ grep /proc/modules oprofile
oprofile 17736 -1
look also with dmesg for any error messages.
you can force the driver to use RTC mode, look the documentation, the
FAQ also mention than RTC kernel driver must no be builtin in the kernel
nor loaded if it was built as sdriver, see the FAQ
From: John Levon <levon@mo...> - 2003-09-20 02:05:18
On Fri, Sep 19, 2003 at 04:04:24PM -0700, Jianpeng Dong wrote:
> I read the news arhive, someone mentioned that oprofile only
> supports SMP machines for RH 7.3 (or else 8.0, 9.0). How about the story
> with RH-7.2?
This is nonsense. You are using a Red Hat kernel - that means that any
problems are your problems. Red Hat chose to disable oprofile on RH7.x,
not us. Use a Linus kernel and then it's ours.
If the same point is made twice by the same person, the thread is over.