Please use oprofile-0.9.7 userland tool for profiling
events for CortexA9 board.(ARMv7)
On Fri, Apr 26, 2013 at 01:26:54PM +0100, Maynard Johnson wrote:
> On 04/25/2013 10:18 PM, RocChen wrote:
> > # to configure with kernel 3.3 header, run: ln -sf generated/autogen.h linux/autogen.sh
> > should be:
> > # to configure with kernel 3.3 header, run: cd $KINC/include &&
> > ln -sf generated/autoconf.h linux/autoconf.h
> > On Fri, Apr 26, 2013 at 11:14 AM, RocChen <email@example.com <mailto:firstname.lastname@example.org>> wrote:
> > Hello, every one:
> > I am a newer to the oprofile and I met some problems with the oprofile.
> > I was profiling some applications on the Zynq board (with a dual core Cortex-A9 integratd, Linux kernel 3.3, linaro 12.01 file system).
> > 1. First, I installed the oproile with apt-get, the oprofile version was 0.9.6.
> > I ran the following command lists;
> > > opcontrol --init
> > > opcontrol --setup --event=CPU_CYCLES:1000 --separate=all --no-vmlinux
> > > opcontrol --start-daemon
> > > opcontrol --start
> > > // here my program, namely the jpg2000dec, jpg2000enc, mpeg2dec...
> > > opcontrol --stop
> > > opcontrol --dump
> > > opreport
> Are you running the opcontrol commands in a script or manually from the command line? The Coretex-A9 processor is not supported in oprofile 0.9.6, so I would have expected the opcontrol setup command to fail. It's possible the 'opcontrol --start' command would succeed if ARM is capable of falling back to timer mode. *Will*, on cc, can perhaps answer that. With the proper setup, you should be able to get this to work with oprofile 0.9.7 or later. But I'm not an ARM expert, so hopefully Will can help determine what's not setup correctly.
[adding Koteswararao, who previously reported using OProfile with Zynq]
Timer mode should work fine. If you want to use the PMU, you need to check
that perf is enabled in your kernel (CONFIG_HW_PERF_EVENTS=y) and that your
interrupts are being registered correctly; either via device tree or as a