'\" t .\" Title: fence_signal .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: January 2017 .\" Manual: Device drivers infrastructure .\" Source: Kernel Hackers Manual 4.8.15 .\" Language: English .\" .TH "FENCE_SIGNAL" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "Device drivers infrastructure" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" fence_signal \- signal completion of a fence .SH "SYNOPSIS" .HP \w'int\ fence_signal('u .BI "int fence_signal(struct\ fence\ *\ " "fence" ");" .SH "ARGUMENTS" .PP \fIfence\fR .RS 4 the fence to signal .RE .SH "DESCRIPTION" .PP Signal completion for software callbacks on a fence, this will unblock \fBfence_wait\fR calls and run all the callbacks added with \fBfence_add_callback\fR\&. Can be called multiple times, but since a fence can only go from unsignaled to signaled state, it will only be effective the first time\&. .SH "COPYRIGHT" .br