Re: Announcement: Release Candidate 1 for OProfile 1.0.0

Em Fri, Aug 15, 2014 at 08:06:53PM +0000, Maucci, Cyrille escreveu:
> Hello Maynard,
> 
> So maybe a dumb remark.
> I've got a RHEL6.4 system that I've upgraded the kernel up to 3.15.9.
> perf tools work fine there.
> When I launch the below recompiled operf, it tells me :
> 
> [root@nv34 oprofile-1.0.0-rc1]# operf
> Your kernel's Performance Events Subsystem does not support your processor type.
> 
> How would perf not complain about that but operf would ?

Probably perf is fallbacking to cpu-cycles?

I.e. on a machine with a processor supported, i.e. a HW PMU:

[acme@zoo ~]$ perf record usleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.016 MB perf.data (~684 samples) ]
[acme@zoo ~]$ perf evlist
cycles
[acme@zoo ~]$

We get the 'cycles' event, perfect.

But o a KVM guest:

root@ubuntu13:~# perf record sleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.007 MB perf.data (~288 samples) ]
root@ubuntu13:~# perf evlist
cpu-clock
root@ubuntu13:~# 


I.e. perf tries:

[acme@zoo ~]$ perf list | grep -w cycles
  cpu-cycles OR cycles                               [Hardware event]
<SNIP>

If it fails, it fallbacks to:

[acme@zoo ~]$ perf list | grep -w cpu-clock
  cpu-clock                                          [Software event]
[acme@zoo ~]$

Perhaps this is what is happening.

- Arnaldo

 
> Thanks a lot
> ++Cyrille
> 
> -----Original Message-----
> From: Maynard Johnson [mailto:[email protected]] 
> Sent: Friday, August 15, 2014 5:54 PM
> To: oprofile-list
> Subject: Announcement: Release Candidate 1 for OProfile 1.0.0
> 
> We are pleased to announce OProfile 1.0.0 Release Candidate 1.  You can download this release at:
> 	http://sourceforge.net/projects/oprofile/files/oprofile/oprofile-1.0.0-rc1/
> 
> Please download and test this release candidate, and send your feedback by replying to this message.  Please include your hardware platform and Linux distribution information in your reply.
> 
> Thanks.
> -Maynard Johnson
> 
> -----------------------------------------------------------------
> 
> Release Notes
> ===============
> OProfile 1.0.0 Release Candidate 1 has been released. A major change in this release is the removal of the legacy opcontrol-based profiler.
> This legacy profiling tool has been deprecated since release 0.9.8 when operf was first introduced. The following components and processor types that were dependent on opcontrol have also been removed:
> 
>    - GUI component (i.e., oprof_start)
>    - IBS events removed from AMD processors
>    - All Alpha processors, except for EV67 (which *is* supported by operf/ocount)
>    - Architecture avr32
>    - Architecture ia64
>    - Processor model IBM Cell
>    - Processor model P.A. Semi PA6T
>    - RTC (real time clock mode)
> 
> OProfile users still running on any of these affected systems or needing any of the removed components listed above should not upgrade to OProfile release 1.0. Alternatively, you can obtain all of the new features, enhancements, and bug fixes described below and still have access to opcontrol, by doing the following:
> 
> 	git clone git://git.code.sf.net/p/oprofile/oprofile oprofile
> 	cd oprofile
> 	git checkout PRE_RELEASE_1_0
> 
> and then build/install as usual.
> 
> More information about OProfile can be seen at
>     http://oprofile.sf.net
> 
> 
> Incompatibilities with previous release
> ---------------------------------------
> 
> - Sample data collected with previous releases of OProfile are incompatible
>   with release 1.0.
> - ophelp schema: Major version changed for removal of unit mask 'extra'
>   attribute and addition of unit mask 'name'.
> 
> 
> New features
> ------------
> 
> - Enhance ocount to support millisecond time intervals
> - Obtain kernel symbols from /proc/kallsyms if no vmlinux file specified
> 
> - New/updated Processor Support
>     * (New) Freescale e6500 
>     * (New) Freescale e500mc
>     * (New) Intel Silvermont
>     * (New) ARM ARMv7 Krait
>     * (New) ARM ARMv8 (AArch64)
>     * (New) Intel Broadwell
>     * (New) ARM Cortex A57
>     * (New) ARM Cortex A53
>     * Added little endian support for IBM POWER8
>     * Update events for IBM POWER8
>     * Added edge-detect events for IBM POWER7
>     * Update events for Intel Haswell
> 
> 
> Bug fixes
> ---------
> 
> Filed bug reports:
> -------------------------------------------------------------------------
> |  BUG ID   |  Summary 
> |-----------|-----------------------------------------------------------
> |-----------|-
> |   236     | opreport schema: Fix count field maxOccurs (changed to
> |           | 'unbounded')
> |   245     | Fix compile error on ppc/uClibc platform: 'AT_BASE_PLATFORM'
> |           | undeclared'
> |   248     | Duplicate event specs passed to ocount show up twice in
> |           | output
> |   252     | Fix operf/ocount default unit mask selection
> |   253     | ocount: print the unit mask, kernel and user modes if
> |           | specified for the event
> |   254     | ophelp schema is not included in installed files
> |   255     | Remove unused 'extra' attribute from ophelp schema
> |   256     | opreport from 'operf --callgraph' profile shows false
> |           | recursive calls
> |   257     | Fix handling of default named unit masks longer than 11 chars
> |   259     | Print unit mask name where applicable in ophelp XML output
> |   260     | Fix profiling of multi-threaded apps when using "--pid"
> |           | option
> |   262     | Fix operf/opreport kernel throttling detection
> |   263     | Fix sample attribution problem when using multiple events
> |   266     | exclude/include files option doesn't work for opannotate -a
> -------------------------------------------------------------------------
> 
> Other bug fixes and improvements without a filed report (e.g., posted to the list):
> ---------------
>    - Update Alpha EV67 CPU support and remove all other Alpha CPU support
>    - operf main process improperly killing conversion process
>    - Fix up S390 support to work with operf/ocount
>    - Link ocount with librt for clock_gettime only when needed
>    - Fix 'Invalid argument' running 'opcontrol --start --callgraph=<n>' in
>      Timer mode
>    - Make sure hypervisor is excluded from ocount and operf
>    - operf log may over-report "sample address not in expected range for
>      domain"
>    - Allow root to remove old jitdump files from /tmp/.oprofile/jitdump
>    - Remove opreport warnings for /no-vmlinux, [vdso], [hypervisor_bucket]
>      not found
>    - Fix event codes for marked architected events (IBM ppc64)
>    - Make operf/ocount detect invalid timer mode from opcontrol
>    - Reduce overhead of operf waiting for profiled app to end
>    - Fix "Unable to open cpu_type file for reading" for IBM POWER7+
>    - Allow all native events for IBM POWER8 in POWER7 compat mode
>    - Fix spurious "backtraces skipped due to no file mapping" log entries
>    - Fix the units for the reported CPU frequency
> 
> 
> Known problems and limitations
> -------------------------
> - When using operf to profile multiple events, the absolute number of
>   events recorded may be substantially fewer than expected. This can be
>   due to knwon bug in the Linux kernel's Performance Events Subsystem that
>   was fixed sometime between Linux kernel version 3.1 and 3.5.
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> oprofile-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oprofile-list
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> oprofile-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oprofile-list

----- End forwarded message -----

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