papi /

Filename Size Date modified Message
doc
man
src
238 B
Create a .gitattributes file.
13.4 KB
Update ChangeLog and Release Notes in preparation for the 4.0.0 release.
15.5 KB
Add edited change log for 4.1 release.
17.3 KB
Add new change log for this release.
18.3 KB
Add files for the 4.1.2 release.
123 B
Add minimal changelog.
21.5 KB
Final (?) updates for the 4.1.3 release.
33.3 KB
Update Release Notes and add ChangeLog for PAPI 4.1.4.
45.7 KB
Commits for the 4.2.0 release.
42.4 KB
Update Change Log and release notes for 421 release.
5.3 KB
Pickup the changelog from papi 4.4
102.3 KB
Changelog for PAPI5
3.7 KB
Update releasenotes and add a changelog for 5.0.1
19.3 KB
Turns out we are calling this 5.1.0.2
7.9 KB
Grab the updated ChangeLog from 5.1.1
60.2 KB
Update RELEASENOTES and create a Changelog for 5.2
19.8 KB
Update the 5.3 ChangeLog
3.8 KB
Generate a changelog for 5.3.2
26.1 KB
Generate a changelog for 5.4.0
11.9 KB
Updated ChangeLog and release notes for 5.4.1
13.9 KB
PAPI 5.4.3 release (releasenotes, changelog, man files, ...)
10.2 KB
Release notes and ChangeLogP550 for 5.5.0 release
2.0 KB
Changelog for 5.5.1 release
24.4 KB
Fix leftover doxygen reference in INSTALL file.
1.9 KB
Change copyright years to include 2010.
38.4 KB
Small update to FAQ to fix mailing list references
3.0 KB
Make README the same as README.md
3.0 KB
README.md edited online with Bitbucket
56.2 KB
Fixing the date in the RELEASENOTES file.
481 B
Fulltest disabled in bitbucket-pipelines.yml (edited online with Bitbucket)
415 B
Add the bitbucket-pipelines.yml to the list of files to be deleted
4.7 KB
The python script that is used to create a ChangeLog for the
2.8 KB
Bump papi version to 5.5.2 after release.
6.2 KB
Bump papi version to 5.5.2 after release.

PAPI: Performance Application Programming Interface

Innovative Computing Lab

University of Tennessee, Knoxville, TN



About

PAPI provides the tool designer and application engineer with a consistent interface and methodology for use of the performance counter hardware found in most major microprocessors. PAPI enables software engineers to see, in near real time, the relation between software performance and processor events.

In addition, PAPI provides access to a collection of components that expose performance measurement opportunites across the hardware and software stack.

Getting Started

If this is the first file you've opened in the PAPI tree, we'll try to give you a few tips on where to go from here.

  • Read the license found in LICENSE.txt. It's pretty short, and not very restrictive, but it'll give you an idea of what you can and can't do with the PAPI sources.
  • Visit the website at: http://icl.utk.edu/papi There you can find late-breaking news that may be more current than in these files. You can also find documentation in a greater variety of formats than in the papi/doc/ directory.
  • Sign up for the PAPI mailing list(s). Instructions are on our home page.
  • Read the RELEASENOTES.txt file to get an idea of what's new in the current release.

Installing PAPI

To install PAPI on your system:

  • Find the section in INSTALL.txt that pertains to your hardware and operating system.
  • Follow the directions to install required components and build the PAPI libraries.
  • Run the test suite when you are finished to verify that everything went ok. NOTE: Although we make every attempt to get all tests to PASS or SKIP on all platforms, there are occasional instances of FAILures due to excessively tight compliance thresholds or platform idiosyncrasies. Don't panic if one or two tests FAIL. Contact us with complete output and we'll see what we can do.

Using PAPI

To use PAPI in your own programs:

  • Read the PAPI Overview found at: http://icl.utk.edu/projects/papi/wiki/Main_Page.
  • Try out the utility programs in /utils to see what's in your system.
  • Try a test program. Source for a number of tests in both C and FORTRAN is available in the src/tests/ and src/ftests/ directories. Find a program that's similar to what you want to do. Make sure you can build it and run it.
  • Write a test program of your own, exercising the PAPI events and features of interest to you.
  • Go for broke. Fold PAPI calls into your sources and see what you can learn.

Bugs and Questions