Re: Announcement: Release Candidate 1 for OProfile 1.0.0
William Cohen <[email protected]>
| Newsgroups | gmane.linux.oprofile |
|---|---|
| Message-ID | <[email protected]> |
On 08/26/2014 11:56 AM, Maynard Johnson wrote:
> On 08/15/2014 10:54 AM, Maynard Johnson wrote:
>> 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.
>
> Fellow oprofile architecture maintainers,
> Please test the oprofile 1.0.0 RC1 and let me know your results. FYI . . . Due to the
> Java profiling bug reported this week by Brian Hall, I will be incorporating a fix into
> the next 1.0.0 tar file I make available. If more fixes are needed, I will put out an
> RC2, otherwise I'll make it GA. Either way, I'd like to put out the next tar file by
> the end of the week. Thanks!
>
> -Maynard
>>
>> Thanks.
>> -Maynard Johnson
Hi Maynard,
I built a rpm using the latest git repo tarball and have been testing that out on a number of different platforms.
There are a number of xml failures in the test results (footnotes (1) and (2)). Have anyone else observed that? Or is this a local build issue?
I also had some issues with the tests running on arm cortex-a9. The perf utility works on the machine but operf and ocount are not. This seems to be specific to the cortex a9 machine things work on a cortex a15 machine.
# operf --events INST_RETIRED:500000:0:1:1,CPU_CYCLES:500000:0:1:1, workloads/thread_src/thread_bin
perf_event_open failed with Operation not supported
Caught runtime_error: Internal Error. Perf event setup failed.
Error running profiler
Below is a list of machine ran tests on and notes about the test results.
-Will
Fedora20
i386/ivybridge
oprofile-operf tests failures (1)
oprofile-single_process failure (1)
x86_64/family10
no failures seen unlike the i386/ivybridge
arm/ca15
oprofile-operf tests failures (1)
oprofile-single_process failure (1)
arm/ca9
ocount-cycle-check-run.exp failed because of CPU freq not reported
ERROR: tcl error sourcing ./oprofile-operf/oprofile-operf-run.exp.
perf does work on the machine, but for some reason oper was having problems setting up the hardware:
rawhide in kvm guest copying host cpuid, host running fedora 20
i386/ivybridge
ocount-cycle-check-run.exp failed because of Turbo mode
oprofile-operf tests failures (1)
oprofile-single_process failure (1)
rhel7
i386/ivybridge
oprofile-operf tests failures (1)
oprofile-single_process failure (1)
arm/ca57
ocount-cycle-check-run.exp failed because of CPU freq not reported
oprofile-operf tests failures (1)
oprofile-single_process failure (1)
arm/xgene
ocount-cycle-check-run.exp failed because of CPU freq not reported
oprofile-operf tests failures (1)
oprofile-single_process failure (1)
rhel6
i386/westmere
ocount-cycle-check-run.exp failed because of Turbo mode
oprofile-operf tests failures (2)
oprofile-single_process failure (2)
(1)
Running ./oprofile-operf/oprofile-operf-run.exp ...
FAIL: XML opreport output with callgraph option=1 is invalid
warning: failed to load external entity "/share/doc/oprofile/opreport.xsd"
Schemas parser error : Failed to locate the main schema resource at '//share/doc
/oprofile/opreport.xsd'.
(2)
Running ./oprofile-operf/oprofile-operf-run.exp ...
FAIL: XML opreport output with callgraph option=1 is invalid
out.xml:19: element count: Schemas validity error : Element 'count': This element is not expected. Expected is one of ( symbol, module ).
out.xml fails to validate
>>
>> -----------------------------------------------------------------
>>
>> 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
>>
>
>
> ------------------------------------------------------------------------------
> 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/