RE: Announcement: Release Candidate 1 for OProfile 1.0.0

Hello William,

Sorry I had missed your reply.
What is bizarre is that perf works fine up to 3.9.11 kernel.

Performance counter stats for 'ls':

          1.662938 task-clock                #    0.085 CPUs utilized
                 3 context-switches          #    0.002 M/sec
                 1 cpu-migrations            #    0.601 K/sec
               248 page-faults               #    0.149 M/sec
         3,310,577 cycles                    #    1.991 GHz                     [27.82%]
   <not supported> stalled-cycles-frontend
   <not supported> stalled-cycles-backend
         1,949,533 instructions              #    0.59  insns per cycle         [52.34%]
           174,059 branches                  #  104.670 M/sec
            19,177 branch-misses             #   11.02% of all branches

Once I move to 3.10, it does not work anymore.

Performance counter stats for 'ls':

          1.242282 task-clock                #    0.617 CPUs utilized
                19 context-switches          #    0.015 M/sec
                 0 cpu-migrations            #    0.000 K/sec
               241 page-faults               #    0.194 M/sec
   <not supported> cycles
   <not supported> stalled-cycles-frontend
   <not supported> stalled-cycles-backend
   <not supported> instructions
   <not supported> branches
   <not supported> branch-misses

I have no clue what I am doing wrong when upgrading from 3.9.11 to 3.10.

Thanks
++Cyrille

-----Original Message-----
From: William Cohen [mailto:[email protected]] 
Sent: Monday, August 18, 2014 10:41 PM
To: Carl Love; Maucci, Cyrille
Cc: oprofile-list; Arnaldo Carvalho de Melo
Subject: Re: Announcement: Release Candidate 1 for OProfile 1.0.0

On 08/18/2014 01:36 PM, Carl Love wrote:
> 
> Cyrille:
> 
> OK, it looks like oprofile is there and recognizes your CPU. Not sure
> why you get the message "Your kernel's Performance Events Subsystem does
> not support your processor type" that you reported given that perf is
> there and the ophelp command is recognizing the correct CPU.  
> 
> I assume that when you built the new OProfile 1.0 release you did do the
> make install and verified that the installed operf and ocount tools were
> installed in your path.  
> 
> Maynard will be back on Aug 25.  Maybe he has some additional ideas.
> 
>                 Carl Love

Hi Cyrille,

Yes, make sure that the operf/ophelp being used are actually the ones that you built.  On my machine I have built oprofile-1.0.0-rc1 as an rpm and have it installed.  So the following looks reasonable:

[wcohen@santana SPECS]$ which ophelp
/usr/bin/ophelp
[wcohen@santana SPECS]$ ophelp -v
ophelp: oprofile 1.0.0-rc1 compiled on Aug 18 2014 15:24:24
[wcohen@santana SPECS]$ which operf
/usr/bin/operf
[wcohen@santana SPECS]$ operf -v
operf: oprofile 1.0.0-rc1 compiled on Aug 18 2014 15:24:27

There is mention of that error message in the doc/oprofile.xml. The message is coming from operf.cpp:1486 which is checking to see whether the perf infrastructure works.  One thing to check is to make sure that BIOS is not using the performance monitoring hardware.  IIRC there are some BIOS/FIRMWARE that use the performance monitoring hardware and that might be causing the test of the perf support to fail.  As a more substantial test of perf on the machine you might try something like:

perf stat ls


-Will

> 
> 
> On Mon, 2014-08-18 at 16:56 +0000, Maucci, Cyrille wrote:
>> Carl,
>>
>> Here they are:
>>
>> [root@nv34 ~]# ophelp | head -10;
>> oprofile: available events for CPU type "Core 2"
>>
>> See Intel Architecture Developer's Manual Volume 3B, Appendix A and
>> Intel Architecture Optimization Reference Manual
>>
>> For architectures using unit masks, you may be able to specify
>> unit masks by name.  See 'operf' or 'ocount' man page for more details.
>>
>> CPU_CLK_UNHALTED: (counter: all)
>>         Clock cycles when not halted (min count: 6000)
>>
>> Thanks
>> ++Cyrille
>> -----Original Message-----
>> From: Carl Love [mailto:[email protected]] 
>> Sent: Monday, August 18, 2014 6:40 PM
>> To: Maucci, Cyrille
>> Cc: Arnaldo Carvalho de Melo; oprofile-list
>> Subject: RE: Announcement: Release Candidate 1 for OProfile 1.0.0
>>
>> On Mon, 2014-08-18 at 16:23 +0000, Maucci, Cyrille wrote:
>>> Hey Carl,
>>>
>>>  
>>>
>>> My system is an old HP Proliant DL 380 G5 with those processors.
>>>
>>
>> Cyrille:
>>
>> I checked and the processor is still listed in libop/op_cpu_type.c as a supported CPU type.  
>>
>> What do you get when you type ophelp?  Just need the first 10 or so lines as this will print out all of the supported events, if it works correctly.
>>
>>                 Carl Love
>>
>>>  
>>>
> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> oprofile-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oprofile-list
> 


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