9.2. Types of Interrupts

Hardware interrupts are generated by external hardware devices, such as I/O peripherals (e.g., UART, timers, GPIO) or sensors. Hardware interrupts are often used to signal the processor when data is ready to be processed or when an event requires immediate attention.

Example: A UART interrupt generated when new data arrives in the receive buffer.

Hardware interrupts are signals sent to the CPU from external devices, like sensors or input/output peripherals. These signals prompt the CPU to temporarily stop its current task to respond to an urgent event—most commonly when data is available to be processed. For instance, if a sensor detects motion, it may send a hardware interrupt to let the CPU know it needs to capture that information immediately.

Think of hardware interrupts as a fire alarm going off in a building. When the alarm triggers, everyone must stop what they are doing and address the emergency. Similarly, when a hardware interrupt occurs, the CPU must halt its current operations to deal with the signal from the hardware device.

Software interrupts are generated by software or the running program to request the operating system’s attention or trigger a system call. They are often used for tasks such as process scheduling, system calls, or debugging.

Example: A software interrupt used to invoke a system call for file operations.

Software interrupts are created by programs to signal the operating system that an action needs to be taken. For example, when a program needs to read a file, it can generate a software interrupt that instructs the operating system to perform this action. This is crucial because it allows programs to request services from the operating system without managing the hardware directly.

Consider software interrupts like making a phone call to request assistance. If you're at a restaurant and need help, you call a waiter (the operating system). You don’t go into the kitchen yourself; instead, you signal for help through the interruption of your meal.

Maskable interrupts (IRQ) can be disabled or ignored by the processor if they are not of high priority. These interrupts are typically used for general I/O operations or peripheral events.

Maskable interrupts are ones that can be turned off by the CPU if higher priority tasks need attention first. This provides flexibility, allowing the processor to ignore less critical signals when it's busy handling more important tasks. This mechanism helps in effectively managing multiple signals from various devices without overwhelming the CPU.

Imagine you’re in a meeting where urgent topics are being discussed. If someone at the door is selling cookies (a lower priority interrupt), you might ignore them until the meeting is over or until a break occurs. This represents how a maskable interrupt works.

Non-maskable interrupts (NMI) cannot be disabled or ignored, as they indicate critical system errors or events that must be handled immediately.

Example: A hardware failure interrupt (e.g., memory parity error) that forces immediate attention.

Non-maskable interrupts are urgent signals that require immediate attention from the CPU. Unlike maskable interrupts, they cannot be turned off, as they often indicate critical issues, such as hardware malfunctions that could compromise system integrity. The CPU must prioritize these interrupts to prevent system failures and maintain stability.

These are comparable to emergency sirens that require immediate action—like a tornado alarm. You can’t ignore it; you must respond quickly for safety. Similarly, a non-maskable interrupt signals the CPU to act without delay.

--