OS & Hardware

What is the role of an interrupt vector table?

  1. ARecording how many times each type of interrupt has occurred
  2. BSpecifying the address where handling begins for each type of interrupt or exception
  3. CRecording the order in which processes will run next
Show answer and explanation

Answer: B. Specifying the address where handling begins for each type of interrupt or exception

When an interrupt or exception occurs, the CPU obtains a number (vector) for its cause, reads the handler's start address from the interrupt vector table and jumps there. The OS fills in the table at boot so that the timer, each device, page faults, system calls and so on can invoke separate handlers. Counting occurrences is a separate statistics mechanism, and the order of processes is managed by the OS scheduler.

  • A. Counting occurrences is a separate statistics mechanism.
  • B. Correct. It maps each cause to the start address of its handler.
  • C. The order of processes is managed by the scheduler.
Practice this topic Back to topic

More OS & Hardware questions

  1. What should you keep in mind when temporarily disabling (masking) interrupts during a critical section?
  2. Why is interrupt handling split into a short part done immediately and the remainder done later in a normal context?
  3. What is the role of a page table?
  4. When does a page fault occur?
  5. When a page fault occurs on a page that was evicted to disk, what does the OS do?