Linked from

The 15 pages that link to Interrupt, each with the reason it gives.

• Embedded systemRelated: Hardware interrupts let a system respond promptly to changing inputs.

• Operating systemRelated: Hardware interrupts alert the operating system to events such as device completion.

• MicrocontrollerRelated: Interrupts let a microcontroller respond promptly to external changes.

• Device driverRelated: Devices use interrupts to notify drivers that work has completed or needs attention.

• Direct memory accessRelated: Devices commonly interrupt the processor when a DMA transfer completes.

• System callCompared with: Unlike a hardware interrupt, a system call is initiated synchronously by the running program.

• Digital signal processorRelated: Interrupts let a DSP respond promptly to incoming samples and hardware events.

• Memory-mapped I/ORelated: Mapped status registers commonly help software identify the device event that triggered an interrupt.

• BIOSNarrower topic: BIOS services historically provided software access to hardware through interrupt routines.

• Program counterRelated: Interrupt handling saves execution state, including the address needed to resume.

• DOSRelated: DOS programs use software interrupts to request operating-system services.

• Input/outputRelated: Devices use interrupts to notify the processor that an I/O event needs attention.

• System softwareRelated: Interrupts let devices and software events demand timely attention from the operating system.

• MicrocomputerRelated: Interrupts let microcomputers respond to timers and peripheral devices.

• Computer multitaskingRelated: Timer interrupts let an operating system regain control and switch tasks.