File: PAPI_sprofil.3

package info (click to toggle)
papi 6.0.0~dfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 11,056 kB
  • sloc: ansic: 103,847; fortran: 3,015; xml: 2,460; cpp: 1,845; f90: 1,360; makefile: 977; sh: 591; python: 274
file content (120 lines) | stat: -rw-r--r-- 4,577 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
.TH "PAPI_sprofil" 3 "Thu Feb 27 2020" "Version 6.0.0.0" "PAPI" \" -*- nroff -*-
.ad l
.nh
.SH NAME
PAPI_sprofil \- 
.PP
Generate PC histogram data from multiple code regions where hardware counter overflow occurs\&.  

.SH SYNOPSIS
.br
.PP
.SH "Detailed Description"
.PP 

.PP
\fBC Interface:\fP
.RS 4
#include <\fBpapi\&.h\fP> 
.br
 int \fBPAPI_sprofil( PAPI_sprofil_t * prof, int profcnt, int EventSet, int EventCode, int threshold, int flags )\fP;
.RE
.PP
\fBParameters:\fP
.RS 4
\fI*prof\fP pointer to an array of \fBPAPI_sprofil_t\fP structures\&. Each copy of the structure contains the following: 
.PD 0

.IP "\(bu" 2
buf -- pointer to a buffer of bufsiz bytes in which the histogram counts are stored in an array of unsigned short, unsigned int, or unsigned long long values, or 'buckets'\&. The size of the buckets is determined by values in the flags argument\&. 
.IP "\(bu" 2
bufsiz -- the size of the histogram buffer in bytes\&. It is computed from the length of the code region to be profiled, the size of the buckets, and the scale factor as discussed below\&. 
.IP "\(bu" 2
offset -- the start address of the region to be profiled\&. 
.IP "\(bu" 2
scale -- broadly and historically speaking, a contraction factor that indicates how much smaller the histogram buffer is than the region to be profiled\&. More precisely, scale is interpreted as an unsigned 16-bit fixed-point fraction with the decimal point implied on the left\&. Its value is the reciprocal of the number of addresses in a subdivision, per counter of histogram buffer\&.
.PP
.br
\fIprofcnt\fP number of structures in the prof array for hardware profiling\&. 
.br
\fIEventSet\fP The PAPI EventSet to profile\&. This EventSet is marked as profiling-ready, but profiling doesn't actually start until a \fBPAPI_start()\fP call is issued\&. 
.br
\fIEventCode\fP Code of the Event in the EventSet to profile\&. This event must already be a member of the EventSet\&. 
.br
\fIthreshold\fP 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\&. 
.br
\fIflags\fP bit pattern to control profiling behavior\&. Defined values are given in a table in the documentation for PAPI_pofil  
 
    
.RE
.PP
\fBReturn values:\fP
.RS 4
\fIReturn\fP values for \fBPAPI_sprofil()\fP are identical to those for \fBPAPI_profil\fP\&. Please refer to that page for further details\&.  
 
    
.RE
.PP
\fBPAPI_sprofil()\fP 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 \fBPAPI_profil()\fP\&. For more information on profiling, \fBPAPI_profil\fP  
 
    
.PP
\fBExample:\fP
.RS 4

.PP
.nf
* int retval;
* unsigned long length;
* PAPI_exe_info_t *prginfo;
* unsigned short *profbuf1, *profbuf2, profbucket;
* PAPI_sprofil_t sprof[3];
*
* prginfo = PAPI_get_executable_info();
* if (prginfo == NULL) handle_error( NULL );
* length = (unsigned long)(prginfo->text_end - prginfo->text_start);
* // Allocate 2 buffers of equal length
* profbuf1 = (unsigned short *)malloc(length);
* profbuf2 = (unsigned short *)malloc(length);
* if ((profbuf1 == NULL) || (profbuf2 == NULL))
*   handle_error( NULL );
* memset(profbuf1,0x00,length);
* memset(profbuf2,0x00,length);
* // First buffer
* sprof[0]\&.pr_base = profbuf1;
* sprof[0]\&.pr_size = length;
* sprof[0]\&.pr_off = (caddr_t) DO_FLOPS;
* sprof[0]\&.pr_scale = 0x10000;
* // Second buffer
* sprof[1]\&.pr_base = profbuf2;
* sprof[1]\&.pr_size = length;
* sprof[1]\&.pr_off = (caddr_t) DO_READS;
* sprof[1]\&.pr_scale = 0x10000;
* // Overflow bucket
* sprof[2]\&.pr_base = profbucket;
* sprof[2]\&.pr_size = 1;
* sprof[2]\&.pr_off = 0;
* sprof[2]\&.pr_scale = 0x0002;
* retval = PAPI_sprofil(sprof, EventSet, PAPI_FP_INS, 1000000,
* PAPI_PROFIL_POSIX | PAPI_PROFIL_BUCKET_16)) != PAPI_OK)
* if ( retval != PAPI_OK ) handle_error( retval );
* 

.fi
.PP
.RE
.PP
\fBSee Also:\fP
.RS 4
\fBPAPI_overflow\fP 
.PP
\fBPAPI_get_executable_info\fP 
.PP
\fBPAPI_profil\fP 
.RE
.PP


.SH "Author"
.PP 
Generated automatically by Doxygen for PAPI from the source code\&.