1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>synchronize_hardirq</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="The Linux Kernel API"><link rel="up" href="hardware.html#idp1125715868" title="Interrupt Handling"><link rel="prev" href="hardware.html" title="Chapter&#160;9.&#160;Hardware Interfaces"><link rel="next" href="API-synchronize-irq.html" title="synchronize_irq"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">synchronize_hardirq</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="hardware.html">Prev</a>&#160;</td><th width="60%" align="center">Interrupt Handling</th><td width="20%" align="right">&#160;<a accesskey="n" href="API-synchronize-irq.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-synchronize-hardirq"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>synchronize_hardirq &#8212; 
2  wait for pending hard IRQ handlers (on other CPUs)
3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" class="funcprototype-table" summary="Function synopsis" style="cellspacing: 0; cellpadding: 0;"><tr><td><code class="funcdef">bool <b class="fsfunc">synchronize_hardirq </b>(</code></td><td>unsigned int <var class="pdparam">irq</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer">&#160;</div></div></div><div class="refsect1"><a name="idp1125720980"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>irq</code></em></span></dt><dd><p>
4     interrupt number to wait for
5    </p></dd></dl></div></div><div class="refsect1"><a name="idp1125722588"></a><h2>Description</h2><p>
6   This function waits for any pending hard IRQ handlers for this
7   interrupt to complete before returning. If you use this
8   function while holding a resource the IRQ handler may need you
9   will deadlock. It does not take associated threaded handlers
10   into account.
11   </p><p>
12
13   Do not use this for shutdown scenarios where you must be sure
14   that all parts (hardirq and threaded handler) have completed.
15</p></div><div class="refsect1"><a name="idp1125723740"></a><h2>Returns</h2><p>
16   false if a threaded handler is active.
17   </p><p>
18
19   This function may be called - with care - from IRQ context.
20</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="hardware.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="hardware.html#idp1125715868">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="API-synchronize-irq.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter&#160;9.&#160;Hardware Interfaces&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;<span class="phrase">synchronize_irq</span></td></tr></table></div></body></html>
21