From: Matt Hoosier <mwhoosier@gm...> - 2006-10-05 20:09:31
I've checked out oprofile from CVS, and built for an XScale (ARM)
processor using a kernel based on 2.6.12.
The daemon starts ok:
/ # opcontrol --vmlinux=/home/me/vmlinux-2.6.12.eabi
/ # opcontrol --start
Using 2.6+ OProfile kernel interface
Then, I ran some Gtk+ user interface processes on the system. Later,
opreport doesn't seem to know anything about the activity which
happened outside the kernel:
/ # opreport -l
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
7205014 99.4734 no-vmlinux
38144 0.5266 vmlinux-2.6.12.eabi
Have I missed a step to enable mapping of CPU cycles back to the
user-space processes? Alternately, the estimate of 0 MHz makes me
wonder whether there's low-level trouble with support for this CPU.
Get latest updates about Open Source Projects, Conferences and News.