Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
doku:papi_ir [2016/07/06 10:29] – [Interfacing with PAPI : Low level interface] ir | doku:papi_ir [Unknown date] (current) – external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 29: | Line 29: | ||
In general, some code section to be analyzed with PAPI needs to be wrapped into a sequence of standard PAPI calls. | In general, some code section to be analyzed with PAPI needs to be wrapped into a sequence of standard PAPI calls. | ||
Here, code examples for | Here, code examples for | ||
- | * [[doku: | + | * [[doku: |
- | * [[doku: | + | * [[doku: |
As stated in the comment of the C code above, it is best to analyze one particular event at a time. This advice is given because the CPU has limitations in combining arbitrary counters at a time. | As stated in the comment of the C code above, it is best to analyze one particular event at a time. This advice is given because the CPU has limitations in combining arbitrary counters at a time. | ||
==== Interfacing with PAPI : High level interface ==== | ==== Interfacing with PAPI : High level interface ==== | ||
- | The high-level API combines the counters for a specified list of PAPI preset events, only. The set of implemented high level functions is quite limited and can be found in the section '' | + | The high-level API combines the counters for a specified list of PAPI preset events, only. The set of implemented high level functions is quite limited and can be found in the section '' |
- | * [[doku: | + | |
- | * [[doku: | + | |
- | + | ||
==== Practical tips: ==== | ==== Practical tips: ==== | ||
* A quick overview of supported events and corresponding PAPI variables for a particular type of CPU is obtained from executing command '' | * A quick overview of supported events and corresponding PAPI variables for a particular type of CPU is obtained from executing command '' |