Re: Bringing up oprofile on ARM: opreport prints garbage

[Brian C. <br...@co...>]

> > On Mon, Jun 25, 2007 at 04:04:45PM -0700, Brian Cavagnolo wrote:
> >
> > > I'm trying to get oprofile up on an ARM 926ejs target.  I successfully
> > > build and install the kernel with oprofile support and successfully
> > > run opcontrol and oreport.  However, the opreport output has garbage
> > > in the % and symbol name columns.  Any ideas?  Below is a transcript
> > > of my commands and output.  The ping is just to generate some
> > > interesting data.
> >

> On 6/25/07, John Levon <le...@mo...> wrote:
> > First thing to try is ensure you're runnig CVS oprofile. If that still
> > has the same problem you'll have to investigate the problem yourself...

I presume that this is so that I can be on the same page as folks on
this list.  I've checked the latest out from CVS and built it like so:

$ export ROOTFS_PATH=/path/to/arm/rootfs
$ AUTOMAKE=automake-1.7 ACLOCAL=aclocal-1.7 ./autogen.sh
$ ./configure --prefix=/usr/ --with-kernel-support --host=arm-linux
--with-extra-includes=$ROOTFS_PATH/usr/include/
--with-extra-libs=$ROOTFS_PATH/usr/lib/
$ make
$ make install DESTDIR=$ROOTFS_PATH

Next I head over to the target and still get the garbage output.  Note
in the transcript that follows that the garbage output changes in a
subsequent invocation of opreport.  I'll start hunkering down and
reading the internals documentation to try to understand where this
could be coming from.  Any pointers would be appreciated.  Note that
I'm using a vanilla 2.6.20 kernel with CONFIG_PROFILING=y
CONFIG_OPROFILE=m.

Thanks,
Brian

# opcontrol --reset
# opcontrol --vmlinux=/vmlinux
# opcontrol --start
Using 2.6+ OProfile kernel interface.
Reading module info.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.
Profiler running.
# ping -c 5 192.168.0.113
PING 192.168.0.113 (192.168.0.113): 56 data bytes
64 bytes from 192.168.0.113: seq=0 ttl=64 time=429496728.5 ms
64 bytes from 192.168.0.113: seq=1 ttl=64 time=429496728.7 ms
64 bytes from 192.168.0.113: seq=2 ttl=64 time=429496728.8 ms
64 bytes from 192.168.0.113: seq=3 ttl=64 time=429496728.8 ms
64 bytes from 192.168.0.113: seq=4 ttl=64 time=429496728.7 ms

--- 192.168.0.113 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 429496728.5/85899345.0/429496728.8 ms
# opcontrol --shutdown
Stopping profiling.
Killing daemon.
# opreport
CPU: CPU with timer interrupt, speed . MHz (estimated)
Profiling through timer interrupt
          TIMER:0|
  samples|      %|
------------------
     1252 h@@ vmlinux
       13  h@@ ld-uClibc-0.9.29.so
       11  h@@ busybox
        4  h@@ libuClibc-0.9.29.so
        1  h@@ oprofiled
# opreport
CPU: CPU with timer interrupt, speed . MHz (estimated)
Profiling through timer interrupt
          TIMER:0|
  samples|      %|
------------------
     1252 d@ vmlinux
       13  d@ ld-uClibc-0.9.29.so
       11  d@ busybox
        4  d@ libuClibc-0.9.29.so
        1  d@ oprofiled