Interrupt handler

In computer <a href="/facts/Systems_programming/urTteIsW">systems programming</a>, an interrupt handler, also known as an interrupt service routine or ISR, is a special block of code associated with a specific <a href="/facts/Interrupt/Mm6C4rpc">interrupt</a> condition. Interrupt handlers are initiated by hardware interrupts, software interrupt instructions, or software <a href="/facts/Exception_handling/VrJxgb9r">exceptions</a>, and are used for implementing <a href="/facts/Device_driver/rDYnHU1G">device drivers</a> or transitions between protected modes of operation, such as <a href="/facts/System_call/NW44AFJr">system calls</a>.
The traditional form of interrupt handler is the hardware interrupt handler. Hardware interrupts arise from electrical conditions or low-level protocols implemented in <a href="/facts/Digital_logic/RHLulvKI">digital logic</a>, are usually dispatched via a hard-coded table of interrupt vectors, asynchronously to the normal execution stream (as interrupt masking levels permit), often using a separate stack, and automatically entering into a different execution context (privilege level) for the duration of the interrupt handler's execution. In general, hardware interrupts and their handlers are used to handle high-priority conditions that require the interruption of the current code the <a href="/facts/Central_processing_unit/Jxp1bqMV">processor</a> is executing.
Later it was found convenient for software to be able to trigger the same mechanism by means of a software interrupt (a form of synchronous interrupt). Rather than using a hard-coded interrupt dispatch table at the hardware level, software interrupts are often implemented at the <a href="/facts/Operating_system/8XTuvMh2">operating system</a> level as a form of <a href="/facts/Callback_(computer_programming)/vPlrCJXG">callback function</a>.
Interrupt handlers have a multitude of functions, which vary based on what triggered the interrupt and the speed at which the interrupt handler completes its task. For example, pressing a key on a <a href="/facts/Computer_keyboard/MczF9LIS">computer keyboard</a>, or moving the <a href="/facts/Computer_mouse/fJpa1tUE">mouse</a>, triggers interrupts that call interrupt handlers which read the key, or the mouse's position, and copy the associated information into the computer's memory.
An interrupt handler is a low-level counterpart of <a href="/facts/Event_handler/0YdM6AoB">event handlers</a>. However, interrupt handlers have an unusual execution context, many harsh constraints in time and space, and their intrinsically asynchronous nature makes them notoriously difficult to debug by standard practice (reproducible test cases generally don't exist), thus demanding a specialized skillset—an important subset of <a href="/facts/System_programming/urTteIsW">system programming</a>—of software engineers who engage at the hardware interrupt layer.

Interrupt handler open-in-new

Interrupt handler