Blame man/man3/PAPI_lock.3
Branch: 57771707c5d17696fd3660ed6f10428b3c234e9a
Packit
577717
.TH "PAPI_lock" 3 "Mon Dec 18 2017" "Version 5.6.0.0" "PAPI" \" -*- nroff -*-
Packit
577717
.ad l
Packit
577717
.nh
Packit
577717
.SH NAME
Packit
577717
PAPI_lock \-
Packit
577717
.PP
Packit
577717
Lock one of two mutex variables defined in \fBpapi\&.h\fP\&.
Packit
577717
Packit
577717
.SH SYNOPSIS
Packit
577717
.br
Packit
577717
.PP
Packit
577717
.SH "Detailed Description"
Packit
577717
.PP
Packit
577717
\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
577717
.PP
Packit
577717
\fBC Interface:\fP
Packit
577717
.RS 4
Packit
577717
#include <\fBpapi\&.h\fP>
Packit
577717
.br
Packit
577717
void \fBPAPI_lock(int lock)\fP;
Packit
577717
.RE
Packit
577717
.PP
Packit
577717
\fBParameters:\fP
Packit
577717
.RS 4
Packit
577717
\fIlock\fP -- an integer value specifying one of the two user locks: PAPI_USR1_LOCK or PAPI_USR2_LOCK
Packit
577717
.RE
Packit
577717
.PP
Packit
577717
\fBReturns:\fP
Packit
577717
.RS 4
Packit
577717
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
577717
.RE
Packit
577717
.PP
Packit
577717
\fBSee Also:\fP
Packit
577717
.RS 4
Packit
577717
\fBPAPI_unlock\fP
Packit
577717
.PP
Packit
577717
\fBPAPI_thread_init\fP
Packit
577717
.RE
Packit
577717
.PP
Packit
577717
Packit
577717
Packit
577717
.SH "Author"
Packit
577717
.PP
Packit
577717
Generated automatically by Doxygen for PAPI from the source code\&.