Re: Announcement: Release Candidate 1 for OProfile 1.0.0

On Thu, Aug 28, 2014 at 06:22:19PM +0100, Maynard Johnson wrote:
> On 08/28/2014 11:11 AM, William Cohen wrote:
> > 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,
> 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

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