Re: Announcement: Release Candidate 1 for OProfile 1.0.0

On 08/28/2014 02:07 PM, Will Deacon wrote:
> On Thu, Aug 28, 2014 at 06:22:19PM +0100, Maynard Johnson wrote:
>> On 08/28/2014 11:11 AM, William Cohen wrote:

>>> Below is a list of machine ran tests on and notes about the test results.
>> Will,
>> Many thanks for all the testing you've done!  I will defer to Will Deacon
>> on the problem with running operf/ocount on cortex-a9, but I have answers
>> for the XML-related test failures for you.  See below.
> 
> Thanks for giving this a whirl. Which was the A9 SoC you used? The PMU
> interrupts are often not described properly on those, so it could simply be
> that perf hasn't initialised.
> 
> Will
> 

Hi Will,

The working cortex a15 machine is using a locally built 3.15.10 kernel running fedora 20.
Here are some details on the fedora 20 arm cortex a9 machine:

[wcohen@localhost ~]$ uname -a
Linux localhost 3.15.10-200.fc20.armv7hl #1 SMP Thu Aug 14 16:37:46 UTC 2014 armv7l armv7l armv7l GNU/Linux
[wcohen@localhost ~]$ more /proc/cpuinfo
processor	: 0
model name	: ARMv7 Processor rev 0 (v7l)
Features	: swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x1
CPU part	: 0xc09
CPU revision	: 0

processor	: 1
model name	: ARMv7 Processor rev 0 (v7l)
Features	: swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x1
CPU part	: 0xc09
CPU revision	: 0

Hardware	: NVIDIA Tegra SoC (Flattened Device Tree)
Revision	: 0000
Serial		: 0000000000000000

The perf utils seem to work on the machine:

$ perf record ls
...
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.011 MB perf.data (~502 samples) ]

$ perf stat ls
...

 Performance counter stats for 'ls':

          6.077000      task-clock (msec)         #    0.401 CPUs utilized          
                15      context-switches          #    0.002 M/sec                  
                 0      cpu-migrations            #    0.000 K/sec                  
                96      page-faults               #    0.016 M/sec                  
         6,003,324      cycles                    #    0.988 GHz                    
         1,085,235      stalled-cycles-frontend   #   18.08% frontend cycles idle   
         4,600,125      stalled-cycles-backend    #   76.63% backend  cycles idle   
         2,117,086      instructions              #    0.35  insns per cycle        
                                                  #    2.17  stalled cycles per insn
           220,666      branches                  #   36.312 M/sec                  
            94,593      branch-misses             #   42.87% of all branches        

       0.015141693 seconds time elapsed


However, the oprofile commands do not:

$ operf ls
perf_event_open failed with Operation not supported
Caught runtime_error: Internal Error.  Perf event setup failed.
Error running profiler

$ ocount ls
perf_event_open failed with Operation not supported
Caught runtime error while setting up counters
Internal Error.  Perf event setup failed.
Error running ocount




-Will




------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/