Re: OProfile-1.2.0-rc1

Hi William,

I have tested this tarball on a Knights Landing and everything looks good,
except that the testsuite still does not contain my KNL patch I guess.

However, even when I applied the patch to the testsuite, I got:
"Native configuration is x86_64-unknown-linux-gnu"
Is it somehow connected to the testsuite or is that related to the build?
It looks like the events I specified in the testsuite patch for KNL were
used in the test, so I expect it works.

I also ran selected Red Hat tests against it.

Cheers,
Michael

On Mon, 19 Jun 2017, William Cohen wrote:
> There have been a number of improvements checked into the OProfile git repo.  It would be good to have those into an official release.  I have made a release candidate and it would be good to test this out on various platforms.
> 
> URL:
> https://sourceforge.net/projects/oprofile/files/oprofile/oprofile-1.2.0rc1/oprofile-1.2.0rc1.tar.gz/download
> 
> RELEASE NOTES:
> 
> New features
> ------------
> 
> - New/updated Processor Support
>     * ARM Cortex A17
>     * IBM Power 9
>     * IBM Power 8NV and NVL variants
>     * IBM z13
>     * Intel Goldmont
>     * Intel Kabylake
>     * Intel Xeon Phi (Knights Landing)
>     * Achitecture specific events for Applied Micro X-Gene
> 
> Bug fixes
> ---------
> 
> Filed bug reports:
> -------------------------------------------------------------------------
> |  BUG ID   |  Summary 
> |-----------|------------------------------------------------------------
> |  286      | Compilation error: left shift of negative value
> |  288      | oprofile fails to build with --enable-pch and gcc-6.2 
> -------------------------------------------------------------------------
> 
> Other bug fixes and improvements without a filed report (e.g., posted to the lis
> t):
> ---------------
>    - Fixed compile warning and errors when using GCC 6 or GCC 7
>    - Avoid using deprecated readdir_r function
>    - Store samples in the archive and search the appropriate places
>      for samples
>    - Only start the application if the perf events setup was successful
> 
> 
> 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 known bug in the Linux kernel's Performance Events
>   Subsystem that was fixed sometime between Linux kernel version 3.1
>   and 3.5.
> 
> - Monitoring processes that frequently create and destroy threads via
>   the "--pid" option can be problematic.  The pipes used within operf
>   and ocount may fill up can cause these programs to hang and require
>   multiple cntl-C to exit rather than successfully collecting data on
>   fast spawning processes and children.
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> oprofile-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oprofile-list
> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot