Re: Announcement: Release Candidate 1 for OProfile 1.0.0

Maynard Johnson <[email protected]>
Newsgroups gmane.linux.oprofile
Message-ID <[email protected]>
On 08/18/2014 01:46 PM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Aug 18, 2014 at 10:36:01AM -0700, Carl Love escreveu:
>> 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.  
> 
> No, perf is not there, as we determined in this thread, perf is not
> being able, as operf, to access the PMU counter (aka "cycles", aka
> PERF_COUNT_HW_CPU_CYCLES, in oprofile/intel jargon:
> CPU_CLK_UNHALTED.CORE), it is just fallbacking to the software event
> "cpu-clock".
> 
> I.e., perf, on Cyrille's machine, is using this:
> 
> [acme@zoo linux]$ perf list cpu-clock
> 
> List of pre-defined events (to be used in -e):
>   cpu-clock                                          [Software event]
> 
Cyrille, as Arnaldo pointed out, the kernel's Performance Events subsystem does not support your processor type for accessing the hardware event counters, so the perf tool nicely falls back to using the software-defined event, cpu-cycles, which is more or less timer-based.  But operf and ocount support only native hardware events. In a July 23 posting to the oprofile-list (subject "Re: Removal of events for unsupported architectures or processor models"), I said the following:

	Right now, timer mode is supported only with the "legacy" opcontrol-based profiler.
	The operf profiler could, theoretically, support a timer-like option (e.g., configuring
	perf_events with PERF_COUNT_SW_CPU_CLOCK).  I've not been motivated to add this myself,
	but would certainly review patches if anyone would like to contribute such support
	(after 1.0 is released).

-Maynard

> [acme@zoo linux]$
> 
> Because it is not being able to use this one (as, it seems, operf):
> 
> [acme@zoo linux]$ perf list cpu-cycles
> 
> List of pre-defined events (to be used in -e):
>   cpu-cycles OR cycles                               [Hardware event]
> 
> [acme@zoo linux]$
> 
> 
> - Arnaldo
> 
>> 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
>>
>>
>> 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/
> _______________________________________________
> 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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.