| 1 | 8 | ||||||||||||||||||||
| 2 | |||||||||||||||||||||
| 10 | |||||||||||||||||||||
| 3 | |||||||||||||||||||||
| 7 | |||||||||||||||||||||
| 4 | |||||||||||||||||||||
| 5 | 9 | ||||||||||||||||||||
| 6 | |||||||||||||||||||||
1. The time delay between the occurrence of an interrupt and the execution of the corresponding interrupt service routine by the CPU.
2. A memory address pointer pointing to the location of the interrupt service routine that needs to be executed when an interrupt occurs.
3. A signal sent by a hardware device to request attention from the CPU by causing an interrupt to be processed.
4. A programming construct that continuously checks for a specific condition or event until it becomes true.
5. Signals sent from hardware or software to the CPU to temporarily suspend the current operation and handle a specific event or condition.
6. A situation where two or more competing actions are waiting for the other to finish, preventing any of them from completing.
7. The ability of different parts of a program to be executed out of order or in partial order without affecting the final outcome.
8. A situation where the execution of multiple threads or processes in a multitasking system is not synchronized properly, leading to unpredictable outcomes.
9. A technique used by hardware devices to check the status of a peripheral device by sending repeated requests at regular intervals.
10. Interrupts that provide additional information to the CPU about the source, priority, and location of the interrupt service routine to be executed.