1 views collected around this technical thread.
This article explains the role of the interrupt system in ARM‑based Linux platforms, covering hardware modes, vector tables, exception handling, GIC architecture, and kernel integration, and provides detailed code examples and optimization techniques for developers working on embedded and high‑performance systems.
The article explains how early batch-processing systems relied on inefficient polling of slow I/O devices, describes the inspiration from IBM 704's overflow flag, and details the invention and implementation of hardware and software interrupts, including interrupt types, vector tables, and handler functions, to enable efficient CPU‑device interaction.
This article explores the Linux kernel's interrupt management architecture, detailing how hardware interrupt IDs are mapped to software IRQ numbers through the irq_domain structure, GIC controller design, and various mapping strategies such as linear, radix‑tree, and no‑map approaches.
This article explains the ARM hardware interrupt flow, the Linux kernel's handling of IRQ and FIQ, the construction of exception vector tables, the role of asmlinkage, interrupt registration, shared interrupt models, and the specific implementation for the S3C2410 platform.
During a computer freeze, the CPU isn’t simply idle; it may be trapped in a high‑priority interrupt handler or deadlocked kernel code, and the operating system’s scheduling and interrupt priorities determine whether the processor can be reclaimed, explaining why a simple infinite loop rarely causes a crash.
The article explains why computers appear to freeze by describing how the CPU, pre‑emptive multitasking, interrupt handling, and kernel‑level deadlocks interact, showing that simple infinite loops rarely cause a crash while kernel bugs can make the system unresponsive.
This article explains how a CPU handles interrupts using mechanisms like the programmable interrupt controller (PIC), advanced APIC, interrupt vectors, IDT, and how interrupt affinity and CPU affinity can be configured to balance load across multiple cores, illustrating both synchronous exceptions and asynchronous interrupts.
This article explains the layered architecture of the Linux network stack, maps the TCP/IP model to Linux implementation, and details how hardware and soft interrupts, ksoftirqd threads, and NAPI cooperate with driver initialization to process packet reception and transmission.
This article explains the CPU's interrupt mechanism, describing how hardware devices trigger interrupts, the role of the 8259A programmable interrupt controller, the evolution to APIC with I/O and Local APICs, and how interrupt affinity can be configured to improve multi‑core performance.
This article explains what an IDT is, how it is initialized, the structure of interrupt descriptor entries and gates, the implementation of traditional system calls via int 0x80, and the setup and handling of hardware interrupts in the Linux kernel.
This article explains what CPU interrupts are, distinguishes synchronous and asynchronous types, describes the role of APIC controllers, and details the step‑by‑step initialization of the Interrupt Descriptor Table and related interrupt handling mechanisms in the Linux kernel.
This article explains why a Janus gateway’s QPS stalled under large payloads, how enabling NIC multi‑queue and binding interrupts to specific CPUs (IRQ affinity) resolves the bottleneck, and provides practical commands and a script for Linux network interrupt tuning.