PAPI 7.1.0.0
|
Generate PC histogram data from multiple code regions where hardware counter overflow occurs. More...
*prof | pointer to an array of PAPI_sprofil_t structures. Each copy of the structure contains the following:
|
profcnt | number of structures in the prof array for hardware profiling. |
EventSet | The PAPI EventSet to profile. This EventSet is marked as profiling-ready, but profiling doesn't actually start until a PAPI_start() call is issued. |
EventCode | Code of the Event in the EventSet to profile. This event must already be a member of the EventSet. |
threshold | minimum number of events that must occur before the PC is sampled. If hardware overflow is supported for your component, this threshold will trigger an interrupt when reached. Otherwise, the counters will be sampled periodically and the PC will be recorded for the first sample that exceeds the threshold. If the value of threshold is 0, profiling will be disabled for this event. |
flags | bit pattern to control profiling behavior. Defined values are given in a table in the documentation for PAPI_pofil |
Return | values for PAPI_sprofil() are identical to those for PAPI_profil. Please refer to that page for further details. |
PAPI_sprofil() is a structure driven profiler that profiles one or more disjoint regions of code in a single call. It accepts a pointer to a preinitialized array of sprofil structures, and initiates profiling based on the values contained in the array. Each structure in the array defines the profiling parameters that are normally passed to PAPI_profil(). For more information on profiling, PAPI_profil