Writing an Interrupt Handler

Parent topic: Writing an Interrupt Handler

Advanced topics

Now that we've seen the basics of handling interrupts, let's take a look at some more details and some advanced topics.

Interrupt environment
When your ISR is running, it runs in the context of the process that attached it, except with a different stack.
Ordering of shared interrupts
Interrupt latency
Another factor of concern for realtime systems is the amount of time taken between the generation of the hardware interrupt and the first line of code executed by the ISR.
Atomic operations
Some convenience functions are defined in the include file <atomic.h> that allow you to perform atomic operations (i.e., operations that are guaranteed to be indivisible or uninterruptible).
Interrupts and power management
In order to help the kernel save power, you can make an interrupt “lazy” by specifying an acceptable latency for it.

Related concepts

Interrupt handling (System Architecture)

Interrupts (Getting Started with QNX Neutrino)

Related reference

InterruptAttachEvent()

InterruptAttach()

InterruptDetach()

InterruptDisable()

InterruptEnable()

InterruptHookIdle2()

InterruptHookTrace()

InterruptLock()

InterruptMask()

InterruptUnlock()

InterruptUnmask()

InterruptWait()

Parent topic: Writing an Interrupt Handler