Interrupt
An interrupt is an event or signal that breaks ongoing activity and redirects execution or attention so a condition can be handled.
Modern C, Third Edition
A hardware interrupt is an execution event caused synchronously by a processor-detected fault or hardware condition.
- How it is used
- Introduces hardware interrupts as processor-detected exceptional events handled through a signal-handling abstraction.
- How deep it goes
- Explains fault-triggered dispatch through an interrupt vector table and its portability limitations.
- Examples
- Uses division by zero, nonexistent memory, and misaligned wider-integer accesses as fault examples.
- What you can do after
- Evaluate and understand how a processor fault redirects execution to an interrupt handler.
Rust in Action: Systems programming concepts and techniques
A hardware interrupt is an asynchronous request from a hardware device that causes a processor to suspend or redirect its current execution to handle an event.
- How it is used
- Connects device notifications to CPU control flow and operating-system responses.
- How deep it goes
- Explains notification and handler flow, but models interrupts with signals rather than manipulating the kernel directly.
- Examples
- Illustrates a keyboard interrupt during integer addition and a kernel idle loop using HLT.
- What you can do after
- Understand how a device interrupt redirects execution and why it can change a program’s elapsed time.
Read how Rust in Action: Systems programming concepts and techniques explains interrupt →
Latency
A hardware interrupt is an interrupt signal generated by hardware to request operating-system processing.
- How it is used
- Explains interrupt interference when designing low-latency applications.
- How deep it goes
- Explains handlers, deferred processing, and polling trade-offs without detailing interrupt internals.
- Examples
- Uses packet arrivals, completed I/O, and timer events to illustrate interrupt triggers.
- What you can do after
- Evaluate interrupt-related latency and compare polling with interrupt-driven processing.
The Coder Cafe
An interrupt is a hardware or software signal that requests immediate processor attention for an event or condition.
- How it is used
- Explains how processors receive attention requests from devices, system calls, and exceptions during operating-system execution.
- How deep it goes
- Defines hardware, software, and maskable interrupts with examples but does not detail interrupt-handler internals.
- Examples
- Uses mouse movement, received network packets, process creation, segmentation faults, and CPU lockups as concrete examples.
- What you can do after
- Evaluate/understand how interrupt behavior provides evidence when diagnosing low-level operating-system lockups.
Grokking Concurrency
A hardware interrupt is an interrupt generated by a hardware device or controller to request processor attention.
- How it is used
- Explains how interrupts support preemptive multitasking by stopping a task so another can run.
- How deep it goes
- Defines interrupt types and gives examples, but does not explain interrupt-handler internals.
- Examples
- Uses a keyboard button press, file-write completion, and a timer tick as interrupt examples.
- What you can do after
- Understand how device and timer signals can interrupt task execution during multitasking.
Embedded Software with Rust
An interrupt is a hardware or software event that requests processor attention and can trigger execution of an associated handler.
- How it is used
- Explains peripheral events as a firmware concurrency mechanism and shows how Cortex-M handles them.
- How deep it goes
- Distinguishes exceptions from interrupts and traces vector dispatch and context preservation, while deferring detailed sharing APIs.
- Examples
- Uses timer expiry, data arrival, GPIO, and communication peripherals to illustrate interrupt sources and events.
- What you can do after
- Understand how Cortex-M dispatches handlers and why interrupt-shared state needs controlled access.
Also covered in
- The Creative Programmer
- Robotics for ProgrammersIn early access (MEAP)
- Learn Concurrent Programming with Go
- C++ Concurrency in Action, Second Edition
- Interview Speak
- Think Like a Software Engineering Manager
- Classic Game Programming on the NES: Make your own retro video game
What to know first
- CPUA central processing unit (CPU) is a computer processor that executes program instructions and performs general-purpose computational operations.
- threadA thread is a distinct sequence of execution with its own control flow and state, managed or scheduled by a processor, runtime, or operating system.
- developer productivityDeveloper productivity is the amount or value of useful software work developers produce relative to the time, effort, or resources required.
- psychological stressPsychological stress is a state of mental or emotional strain arising from perceived demands, threats, challenges, or adverse circumstances.
Related concepts
- flow statecontrasts with · A flow state is a condition of deeply absorbed, sustained focus and intrinsically rewarding engagement in an activity, with reduced awareness of distractions.
- CPUproduced by · A central processing unit (CPU) is a computer processor that executes program instructions and performs general-purpose computational operations.
- developer productivityproduces · Developer productivity is the amount or value of useful software work developers produce relative to the time, effort, or resources required.
- exceptionincludes · An exception is a runtime signal or value representing an abnormal condition that interrupts ordinary program flow and can be handled or propagated.
- interrupt handleruses · An interrupt handler is a routine automatically invoked in response to a hardware or software interrupt to process the associated event.
Questions about interrupt
What is interrupt?
An interrupt is an event or signal that breaks ongoing activity and redirects execution or attention so a condition can be handled.
Which Manning books explain interrupt?
Modern C, Third Edition, Rust in Action: Systems programming concepts and techniques, Latency, The Coder Cafe, Grokking Concurrency and Embedded Software with Rust.
What should I know before learning interrupt?
Manning books that teach interrupt usually introduce CPU, thread, developer productivity and psychological stress first.
What is the difference between interrupt and flow state?
An interrupt is an event or signal that breaks ongoing activity and redirects execution or attention so a condition can be handled. A flow state is a condition of deeply absorbed, sustained focus and intrinsically rewarding engagement in an activity, with reduced awareness of distractions.
What kinds of interrupt are there?
Kinds of interrupt include exception.
What is interrupt also called?
Interrupt is also called interruption.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





