Interrupt Request
Subject: Computer and Technology noun /ˈɪn.təˌrʌpt rɪˈkwɛst/ 1 definition
- computer-architecture
- operating-systems
- computer-hardware
- systems-programming
-
Definition (noun)
Entry #145 · UpdatedAn Interrupt Request (IRQ) is a hardware signal or bus message sent by a peripheral device, timer, or controller to instruct a processor (CPU) to temporarily pause its current execution and handle an asynchronous event. When an unmasked IRQ is raised, an interrupt controller arbitrates its priority and delivers an interrupt vector to the CPU, which saves its register context, executes the mapped Interrupt Service Routine (ISR), and then restores the interrupted task. Unlike synchronous software system calls or continuous polling loops, an IRQ provides an event-driven hardware boundary that frees the processor to run useful work until a device actually requires attention.
Common Forms
Maskable Hardware IRQ: A standard peripheral interrupt signal that the processor can temporarily ignore or defer using interrupt-enable flags or controller masks while executing critical, atomic code sections.
Non-Maskable Interrupt (NMI) Request: A highest-priority hardware signal that bypasses processor masking flags to demand immediate execution, typically reserved for severe hardware faults, memory parity errors, or watchdog timers.
Line-Based (Edge- and Level-Triggered) IRQ: A dedicated or shared physical signal line—managed by controllers such as a PIC or I/O APIC—that triggers either on a voltage transition (edge-triggered) or while held active until the device is serviced (level-triggered).
Message Signaled Interrupt (MSI / MSI-X): An in-band transaction on buses such as PCI Express where a device performs a targeted memory write instead of asserting a physical wire, avoiding shared-line contention and routing vectors directly to specific CPU cores.
Example
When a 10 Gbps network interface card receives an incoming Ethernet frame and copies it into system RAM via DMA, it issues an MSI-X interrupt request to CPU core 2 by writing a preassigned vector value to the local APIC address. The core pauses its running user thread, saves its registers, invokes the network driver's interrupt handler to enqueue the packet for TCP/IP processing, and then returns to the interrupted application.