9.5. Interrupt Handling Mechanisms

In a vectored interrupt system, each interrupt has a unique entry in the interrupt vector table, pointing directly to the corresponding ISR. This makes the system fast and efficient when determining which interrupt service routine to execute.

Vectored interrupts use an interrupt vector table, which is essentially an indexed list of memory addresses. Each type of interrupt corresponds to an entry in this table. When an interrupt occurs, the CPU can quickly reference the table to find the address of the appropriate Interrupt Service Routine (ISR) to handle that specific interrupt. Because it directly points to the right ISR, the response time is very quick, making this system efficient in handling interrupts.

Think of it like a directory of phone numbers. If you want to call someone, instead of searching through a long list, you can quickly look them up in the directory (the vector table) that tells you their number (the ISR). This allows for fast and organized communication, similar to how vectored interrupts allow quick access to the necessary handling code.

Non-vectored interrupts do not have a specific address for each interrupt. Instead, the ISR address is shared, and the processor must check the interrupt source to determine which action to take.

In non-vectored interrupt systems, there is not a dedicated memory address for every interrupt. Instead, when an interrupt occurs, there is a single ISR that will handle the request. The processor first executes this common ISR and then determines which specific interrupt occurred by checking the status of the hardware devices. This could introduce delays since the processor must identify the exact source of the interrupt before taking action.

Imagine a customer service center where every call goes to a single operator. The operator then asks callers about their issues before directing them to the right department. This is less efficient than having a dedicated line for each department since the operator has to spend time figuring out where to send each call before they can get help.

The ability to mask (disable) specific interrupts allows the system to control which interrupts are processed. This is useful for managing interrupt priorities and avoiding unnecessary context switches during critical operations.

Interrupt masking is a technique used to prevent certain interrupts from interrupting the processor while it is handling a high-priority task. By masking specific interrupts, the system can ensure that only the most critical operations are processed at that moment, allowing the CPU to focus on what is important without interruption. This helps to maintain system stability and performance especially during critical tasks.

Consider a busy chef in a restaurant kitchen. If the chef is preparing a complex dish, they may ask kitchen staff to avoid interrupting them for minor questions or requests (masking those interrupts) until the dish is complete. This allows the chef to focus entirely on the task at hand, ensuring a quality dish without distraction.

--