Lines Matching full:interrupt
40 .Nd "kernel interrupt handler and thread API"
78 The interrupt event API provides methods to manage the registration and
79 execution of interrupt handlers and their associated thread contexts.
81 Each interrupt event in the system corresponds to a single hardware or software
82 interrupt source.
83 Each interrupt event maintains a list of interrupt handlers, sorted by
85 An interrupt event will typically, but not always, have an associated
87 known as the interrupt thread.
91 An interrupt handler contains two distinct handler functions:
98 function is run from interrupt context and is intended to perform quick
99 handling such as acknowledging or masking a hardware interrupt,
102 Both functions are optional; each interrupt handler may choose to register a
104 Each interrupt handler also consists of a name,
123 function executes from the context of the associated interrupt kernel thread.
124 Sleeping is not permitted, but the interrupt thread may be preempted by higher
129 Any memory or zone allocations in an interrupt thread must specify the
133 The exception to these constraints is software interrupt threads, which are
140 function creates a new interrupt event.
161 to specify that this interrupt thread is a software interrupt.
167 interrupt thread's interrupt source.
170 argument is the unique interrupt vector number corresponding to the event.
177 points while handling an interrupt.
187 an interrupt to a particular CPU.
194 argument list that is used to build the base name of the new interrupt thread.
195 The full name of an interrupt thread is formed by concatenating the base
196 name of the interrupt thread with the names of all of its interrupt handlers.
200 function destroys a previously created interrupt event by releasing its
204 An interrupt event can only be destroyed if it has no handlers remaining.
208 function adds a new handler to an existing interrupt event specified by
219 event's interrupt thread.
247 function is the main entry point into the interrupt handling code.
248 It must be called from an interrupt context.
249 The function will execute all filter handlers associated with the interrupt
252 and schedule the associated interrupt thread to run, if applicable.
257 containing the machine state at the time of the interrupt.
264 function removes an interrupt handler from the interrupt event specified by
276 interrupt flags into interrupt thread scheduling priorities.
278 The interrupt flags not related to the type of a particular interrupt
281 interrupt handlers.
284 flag specifies that this handler cannot share an interrupt thread with
292 flag specifies that the interrupt source this handler is tied to is a good
293 source of entropy, and thus that entropy should be gathered when an interrupt
297 flag is not valid for software interrupt handlers.
300 flag specifies that the interrupt ithread may sleep.
314 These callbacks are intended to be defined by the interrupt controller driver,
315 to allow for actions such as masking and unmasking hardware interrupt signals.
317 When an interrupt is triggered, all filters are run to determine if any
318 threaded interrupt handlers should be scheduled for execution by the associated
319 interrupt thread. If no threaded handlers are scheduled, the
321 callback is invoked which should acknowledge the interrupt and permit it to
326 This handler should acknowledge the interrupt, but it should also ensure that
327 the interrupt will not fire continuously until after the threaded handlers have
329 Typically this callback masks level-triggered interrupts in an interrupt
334 callback is invoked from the interrupt thread to enable future interrupts.
335 Typically this callback unmasks level-triggered interrupts in an interrupt
348 function returns a process priority corresponding to the passed in interrupt
410 flag is specified and the interrupt thread
412 already has at least one handler, or the interrupt thread
439 The interrupt event pointed to by
455 There are no interrupt handlers assigned to
458 The interrupt was not acknowledged by any filter and has no associated thread
480 Interrupt threads and their corresponding API first appeared in