Operating System ConceptsSilberschatz and Galvin©19992.1Module 2: Computer-System Structures•Computer System Operation•I/O Structure •Storage Structure•Storage Hierarchy•Hardware Protection•General System ArchitectureOperating System ConceptsSilberschatz and Galvin©19992.2Computer-System ArchitectureOperating System ConceptsSilberschatz and Galvin©19992.3Computer-System Operation•I/O devices and the CPU can execute concurrently.•Each device controller is in charge of a particular device type.•Each device controller has a local buffer.•CPU moves data from/to main memory to/from local buffers•I/O is from the device to local buffer of controller.•Device controller informs CPU that it has finished its operation by causing an interrupt.Operating System ConceptsSilberschatz and Galvin©19992.4Common Functions of Interrupts•Interrupts transfers control to the interrupt service routine generally, through the interrupt vector, which contains the addresses of all the service routines.•Interrupt architecture must save the address of the interrupted instruction.•Incoming interrupts are disabledwhile another interrupt is being processed to prevent a lost interrupt.•A trapis a software-generated interrupt caused either by an error or a user request.•An operating system is interruptdriven.
Operating System ConceptsSilberschatz and Galvin©19992.5Interrupt Handling•The operating system preserves the state of the CPU by storing registers and the program counter.•Determines which type of interrupt has occurred:–polling–vectored interrupt system•Separate segments of code determine what action should be taken for each type of interruptOperating System ConceptsSilberschatz and Galvin©19992.6Interrupt Time Line For a Single Process Doing Output
You've reached the end of your free preview.
Want to read all 6 pages?
- Fall '09
- Operating Systems, Virtual memory, Central processing unit, Interrupt handler