PAPI 5.7.0 Release
PAPI 5.7 is now available. This release includes a new component, called "pcp", which interfaces to the Performance Co-Pilot (PCP). It enables PAPI users to monitor IBM POWER9 hardware performance events, particularly shared “NEST” events without root access.
This release also upgrades the (to date read-only) PAPI “nvml” component with write access to the information and controls exposed via the NVIDIA Management Library. The PAPI “nvml” component now supports both---measuring and capping power usage---on recent NVIDIA GPU architectures (e.g. V100).
We have added power monitoring as well as PMU support for recent Intel architectures such as Cascade Lake, Kaby Lake, Skylake, and Knights Mill (KNM). Furthermore, measuring power usage for AMD Fam17h chips is now available via the “rapl” component.
For specific and detailed information on changes made for this release, see ChangeLogP570.txt for filenames or keywords of interest and change summaries, or go directly to the PAPI git repository.
Some Major Changes for PAPI 5.7 include:
- Added the component PCP (Performance Co-Pilot, IBM) which allows access toPCP events via the PAPI interface.
- Added support for IBM POWER9 processors.
- Added power monitoring support for AMD Fam17h architectures via RAPL.
- Added power capping support for NVIDIA GPUs.
- Added benchmarks and testing for the “nvml” component, which allowspower-management (reporting and setting) for NVIDIA GPUs.
- Re-implementation of the “cuda” component to better handle GPU events,metrics (values computed from multiple events), and NVLink events, each ofwhich have differently handling requirements and may require separate readgroupings.
- Enhanced NVLink support, and added additional tests and example code forNVLink (high-speed GPU interconnect).
- Extension of test suite with more advanced testing: attach_cpu_sys_validate,attach_cpu_validate, event_destroy test, openmp.F test, attach_validate test(rdpmc issue).
Other Changes include:
- ARM64 configuration now works with newer Linux kernels (>=3.19).
- As part of the “cuda” component, expanded CUPTI-only tests to distinguishbetween PAPI or non-PAPI issues with NVIDIA events and metrics.
- Many memory leaks have been corrected. Not all, some 3rd party librarycodes still exhibit memory leaks.
- Better reporting and error handling of bugs. Changes to “infiniband_umad”name reporting to distinguish it from the “infiniband” component.
- Cleaning up of the source code, added documentation and test/utility files.
Acknowledgements: This release is the result of efforts from many people. The PAPI team would like to express special Thanks to Vince Weaver, Stephane Eranian (for libpfm4), William Cohen, Steve Kaufmann, Phil Mucci, and Konstantin Stefanov.
To verify the integrity of the download, check the MD5 hash 'md5sum papi-5.7.0.tar.gz':
Copyright © 2020 The University of Tennessee. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
· Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
· Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer listed in this license in the documentation and/or other materials provided with the distribution.
· Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. in no event shall the copyright owner or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.