2 .\" Copyright (c) 1996 Joerg Wunsch
4 .\" All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
15 .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR
16 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
17 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
18 .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT,
19 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
20 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
21 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
22 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
23 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
24 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
44 .Nd manipulate interrupt priorities
59 .Fn splsoftclock "void"
63 .Fn splstatclock "void"
69 .Fn splx "intrmask_t ipl"
72 This API is deprecated.
73 Use mutexes to protect data structures instead.
81 function family sets the interrupt priority
84 This prevents interrupt handlers of the blocked priority level from
88 part of a driver (the part that runs on behalf of the user process) to
89 examine or modify data areas that might be examined or modified by
92 Each driver that uses interrupts is normally assigned to an interrupt
93 priority group by a keyword in its config line.
95 .Bd -literal -offset indent
96 device foo0 at isa? port 0x0815 irq 12 tty
99 assigns interrupt 12 to the
102 The system automatically arranges for interrupts in
105 group to be called at a priority >=
111 sets the interrupt priority to an absolute value.
113 the value returned by the other functions should be saved in a local
114 variable, and later passed to
116 in order to restore the previous priority.
120 lowers the priority to a value where all interrupt handlers are
121 unblocked, but ASTs (asynchronous system traps) remain blocked until
122 the system is about to return to user mode.
124 The traditional assignment of the various device drivers to the
125 interrupt priority groups can be roughly classified as:
128 Software part of the network interface drivers.
130 All network interface drivers.
134 (i.e., disk and the like) drivers.
136 Basically, all non-network communications devices, but effectively
137 used for all drivers that are neither network nor disks.
144 return the previous priority value.
146 This is a typical example demonstrating the usage:
159 struct foo_softc *sc;
164 if (!(sc->flags & FOO_READY)) {
165 /* Not ready, must sleep on resource. */
166 sc->flags |= FOO_ASLEEP;
167 error = tsleep(sc, PZERO, "foordy", 0);
168 sc->flags &= ~FOO_ASLEEP;
170 sc->flags &= ~FOO_READY;
179 struct foo_softc *sc;
182 sc->flags |= FOO_READY;
183 if (sc->flags & FOO_ASLEEP)
184 /* Somebody was waiting for us, awake him. */
190 Note that the interrupt handler should
192 reduce the priority level.
193 It is automatically called as it had
194 raised the interrupt priority to its own level, i.e., further interrupts
195 of the same group are being blocked.
197 The interrupt priority levels appeared in a very early version of
199 They have been traditionally known by number instead of by
200 names, and were inclusive up to higher priority levels (i.e., priority
201 5 has been blocking everything up to level 5).
202 This is no longer the case in
206 for them is still reflected in the letter
208 of the respective functions and variables, although they are not
209 really levels anymore, but rather different (partially inclusive)
210 sets of functions to be blocked during some periods of the life of
212 The historical number scheme can be considered as a
213 simple linearly ordered set of interrupt priority groups.
215 This manual page was written by