Blame man/man3/PAPI_lock.3

Packit Service a1973e
.TH "PAPI_lock" 3 "Mon Dec 18 2017" "Version 5.6.0.0" "PAPI" \" -*- nroff -*-
Packit Service a1973e
.ad l
Packit Service a1973e
.nh
Packit Service a1973e
.SH NAME
Packit Service a1973e
PAPI_lock \- 
Packit Service a1973e
.PP
Packit Service a1973e
Lock one of two mutex variables defined in \fBpapi\&.h\fP\&.  
Packit Service a1973e
Packit Service a1973e
.SH SYNOPSIS
Packit Service a1973e
.br
Packit Service a1973e
.PP
Packit Service a1973e
.SH "Detailed Description"
Packit Service a1973e
.PP 
Packit Service a1973e
\fBPAPI_lock()\fP grabs access to one of the two PAPI mutex variables\&. This function is provided to the user to have a platform independent call to a (hopefully) efficiently implemented mutex\&.
Packit Service a1973e
.PP
Packit Service a1973e
\fBC Interface:\fP
Packit Service a1973e
.RS 4
Packit Service a1973e
#include <\fBpapi\&.h\fP> 
Packit Service a1973e
.br
Packit Service a1973e
void \fBPAPI_lock(int lock)\fP;
Packit Service a1973e
.RE
Packit Service a1973e
.PP
Packit Service a1973e
\fBParameters:\fP
Packit Service a1973e
.RS 4
Packit Service a1973e
\fIlock\fP -- an integer value specifying one of the two user locks: PAPI_USR1_LOCK or PAPI_USR2_LOCK
Packit Service a1973e
.RE
Packit Service a1973e
.PP
Packit Service a1973e
\fBReturns:\fP
Packit Service a1973e
.RS 4
Packit Service a1973e
There is no return value for this call\&. Upon return from \fBPAPI_lock\fP the current thread has acquired exclusive access to the specified PAPI mutex\&.
Packit Service a1973e
.RE
Packit Service a1973e
.PP
Packit Service a1973e
\fBSee Also:\fP
Packit Service a1973e
.RS 4
Packit Service a1973e
\fBPAPI_unlock\fP 
Packit Service a1973e
.PP
Packit Service a1973e
\fBPAPI_thread_init\fP 
Packit Service a1973e
.RE
Packit Service a1973e
.PP
Packit Service a1973e
Packit Service a1973e
Packit Service a1973e
.SH "Author"
Packit Service a1973e
.PP 
Packit Service a1973e
Generated automatically by Doxygen for PAPI from the source code\&.