Software
Current PAPI Software and Patches
Showing 10-14 of 19 Entries
PAPI 4.2.0 Release
2011-10-26

The PAPI 4.2.0 release is now available for download.

This release now builds for linux platforms using the libpfm4 interface by default. New platform support is provided for AMD Bobcat, Intel SandyBridge, and ARM Cortex A8 and A9. Preliminary support is also provided for MIPS 74K.

We have reviewed and updated all doxygen generated man pages for documentation. Doxygen documentation can be found here.

Several components, particularly the CUDA component, have been updated, and a test environment for component tests has been implemented.

Two new utilities have been added: papi_error_codes and papi_component_avail.

A host of bug fixes and code clean-ups have been implemented.

 

For a summary of changes, read the PAPI 4.2.0  Release Notes.

And for installation instructions read the Installation Notes.
papi-4.2.0.tar.gz   Download View License

PAPI 4.1.4 Release
2011-08-30

The PAPI 4.1.4 release is available for download. This is n internal release of PAPI-C, intended to suppor the Cray toolchain. It contains fixes for several bugs and some newly supported platforms.

This version:

* adds support for Intel SandyBridge processors;
* adds support for ARM Cortex A8 and A9 processors;
* enhances support for NVIDIA CUDA component;
* updates support for libpfm4
* replaces out of date man pages with doxygen generated man pages.

Unless you're curious or in need of one of the above features, we recommend that you wait to upgrade until the release of PAPI 4.2.

For installation instructions read the Installation Notes.

papi-4.1.4.tar.gz   Download View License

PAPI 4.1.3 Release
2011-05-12

The PAPI 4.1.3 release is now available for download. This is a minor release of PAPI-C. It addresses a number of bugs and other issues that have surfaced since the 4.1.2 release. See the software page to download the tarball.

This version:

* adds support for AMD Family 15h (Interlagos) processors;
* adds an NVIDIA CUDA component (pending release of CUDA 4.0);
* adds support for POWER7/AIX.

There are a number of other enhancements and bug fixes included in this version, along with some caveats and known bugs. These are outlined in more detail in the PAPI 4.1.3  Release Notes.

This version bump is a recommended upgrade for anyone using PAPI, but if you aren't seeing any problems with your current installation, it is not required.

For installation instructions read the Installation Notes.

papi-4.1.3.tar.gz   Download View License

PAPI 4.1.2.1 Release
2011-01-21

The PAPI 4.1.2.1 release is now available for download. This is a minor bugfix release of PAPI-C.

This version:

* fixes an error message generated by an invalid PAPI_HW_INT event on Westmere processors

papi-4.1.2.1.tar.gz   Download View License

PAPI 4.1.2 Release
2011-01-20

The PAPI 4.1.2 release is now available for download. This is a minor release of PAPI-C. It addresses a number of bugs and other issues that have surfaced since the 4.1.1 release.

This version:

* fixes an issue with overflows in perf_events in which events would continue to count in the overflow handler. This led to saturation at low thresholds and eventual segfaults;
* fixes a bug in multiplexing that caused sporadic segfaults in some circumstances;
* fixes a situation in which perfctr could add uncountable events;
* fixes various locking and forking issues identified by users;
* adds support for Intel Westmere;
* refreshes support for Matlab and freeBSD;
* refreshes the preset event definitions for Intel Nehalem;

along with a variety of code cleanups and enhancements.

This version bump is a recommended upgrade for anyone using PAPI, but if you aren't seeing any problems with your current installation, it is not required.

For a summary of changes, read the PAPI 4.1.2  Release Notes.


And for installation instructions read the Installation Notes.
papi-4.1.2.tar.gz   Download View License

Showing 10-14 of 19 Entries

Source Code Repository

 

If you would like to interactively browse the PAPI source code, go to the Web based source browser here:
http://icl.cs.utk.edu/trac/papi/browser

This source browser is also accessible through the Trac bug reporting system or directly through the Browse Source link in the menu to the left.

You can also stay up to date directly by cloning a copy of our git Source Code Repository

Make sure git is installed on your machine. You can download a copy here.

Download the PAPI repository the first time with the following command:

> git clone https://icl.cs.utk.edu/git/papi.git

This creates a complete copy of the papi git repository on your computer in a folder called 'papi'.

To make sure your copy is up to date with the repository:

> cd papi
> git pull https://icl.cs.utk.edu/git/papi.git

License

Copyright © 2014 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.

Sep 19 2014 Admin Login