ECE 391 Lecture 6: Interrupt Handling
SchoolUniversity of Illinois
DepartmentElectrical and Computer Engineering
Course CodeECE 391
This preview shows pages 1-2. to view the full 6 pages of the document.
uses one table for invocation of interrupts, Exceptions, System Calls
called the interrupt descriptor table (IDT)
Lower the number, the higher the priority
This is how you connect physical devices to your system
Summary of the basic characteristics of the summary of three fundamental OS services
Lecture 6 - Interrupt Handling
Thursday, February 2, 2017
ECE 391 - Lect Page 1
Only pages 1-2 are available for preview. Some parts have been intentionally blurred.
invalid op-Code or operand
deliberately via int instruction
Thought problem on shared resources
What resources are shared between them?
How might interactions cause problems?
What can we do to fix those problems
interrupt handlers and programs share resources
solution? save them to the stack
will still need to share some things; discussed later
solution? again save them to the stack
external state (e.g., on devices)
compiler optimization (e.g., volatility)
e.g., application waits for interrupt, then observes values written by OS to stack
solution? use separate stack for kernel
This will be important when we work on MP3 (synchronization)
THIS IS BAD…. If you didn't have the problem of Interrupts
step 1: old_head = head
step 2: head = new element;
oops! an interrupt!
ECE 391 - Lect Page 2
You're Reading a Preview
Unlock to view full version