1 / 41

Operating Systems and Computer Organization

Operating Systems and Computer Organization. Chapter 4. Operating System and Computer Organization. Organization of Conventional Computers The ALU The Control Unit The Memory Unit I/O Devices Interrupts Hardware protection. Conventional Computer Organization. Operands. R1. R2. …. Rn.

avak
Download Presentation

Operating Systems and Computer Organization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Operating Systems and Computer Organization Chapter 4 A. Berrached:CMS:UHD

  2. Operating System and Computer Organization • Organization of Conventional Computers • The ALU • The Control Unit • The Memory Unit • I/O Devices • Interrupts • Hardware protection A. Berrached:CMS:UHD

  3. Conventional Computer Organization A. Berrached:CMS:UHD

  4. Operands R1 R2 …. Rn Functional Unit Status Registers Result MDR MAR CMD To/from main memory The ALU A. Berrached:CMS:UHD

  5. Memory Data Access Main Memory A. Berrached:CMS:UHD

  6. Program Specification A. Berrached:CMS:UHD

  7. Machine Language A. Berrached:CMS:UHD

  8. Control Unit A. Berrached:CMS:UHD

  9. Control Unit Operation • Instruction Fetch Phase: instruction is retrieved from memory • Instruction Decode Phase: instruction is decoded and control signals generated • Instruction Execute Phase: ALU op, memory data access, or I/O op is executed. A. Berrached:CMS:UHD

  10. Control Unit Operation PC = <Machine-Start-Address> ; IR = Memory[PC] ; haltFlag = CLEAR ; Decode(IR); while (haltFlag not SET) { Execute(IR); PC = PC + InstructionSize; IR = Memory[PC] ; Decode(IR); } A. Berrached:CMS:UHD

  11. How does it all start? • When the computer is started, the control unit branches to a fixed memory location; e.g. initial PC value hardwired. • The fixed location is a ROM address that contains a the BIOS loader. • The BIOS loader loads a “bootstrap loader” from the disk “boot sector” into memory and branches to the bootstrap loader program. • The bootstrap loader may be comprehensive enough to load the nucleus of the OS; Otherwise, it loads a loader program that does so. • Once bootstrap phase is done, any program can be run by loading it in memory and loading its initial address in the PC (fetch-decode-exec algorithm) A. Berrached:CMS:UHD

  12. 0x0000100 BIOS loader Fetch Unit 0000100 PC Decode Unit IR … Execute Unit Bootstrapping Bootstrap loader (“boot sector”) 1 0x0001000 Primary Memory A. Berrached:CMS:UHD

  13. Fetch Unit 0001000 PC Decode Unit IR … Execute Unit Bootstrapping Bootstrap loader (“boot sector”) 1 0x0000100 2 BIOS loader 0x0001000 0x0008000 Loader Primary Memory A. Berrached:CMS:UHD

  14. Fetch Unit 0008000 PC Decode Unit IR … Execute Unit Bootstrapping Bootstrap loader (“boot sector”) 1 0x0000100 2 BIOS loader 0x0001000 0x0008000 Loader 3 0x000A000 OS Primary Memory A. Berrached:CMS:UHD

  15. Bootstrapping Bootstrap loader (“boot sector”) 1 0x0000100 2 BIOS loader 0x0001000 0x0008000 Fetch Unit Loader 3 000A000 PC 0x000A000 Decode Unit OS IR … Primary Memory Execute Unit 4. Initialize hardware 5. Create user environment 6. … A. Berrached:CMS:UHD

  16. Primary Memory Unit • Main (Primary) Memory holds both program and data while they are being executed by CPU. • The main memory interface consists of the registers: MAR, MDR, CMD. • Unit of information accessed depends on the width of memory and width of data bus. • Max. addressing space depends on width of address bus. • One request at a time. • CPU and I/O devices may contend for memory access. A. Berrached:CMS:UHD

  17. 1234 98765 read 1. Load MAR with address 2. Load Command with “read” 3. Data will then appear in the MDR Primary Memory Unit 0 MAR 1 2 MDR Command 1234 98765 Read Op: n-1 A. Berrached:CMS:UHD

  18. I/O devices • Each I/O device consists of a device controller and the physical device itself. • Devices: - storage devices: for permanent storage (e.g. disk, tape) - communication devices: to transfer data from the computer to another machine (e.g. keyboard, a terminal display, or a serial port to a modem or a network). A. Berrached:CMS:UHD

  19. I/O Devices (cont.) • Device controller: hardware that connects the device to the computer. • continuously monitors and controls the operation of the device. • provides an interface to the computer. • Device Manager: program (part of the OS) that manages device controllers A. Berrached:CMS:UHD

  20. Device manager: Program to manage • device controllers Abstract I/O Machine The Device-Controller-Software Relationship Application Program Software in the CPU Device Controller Device A. Berrached:CMS:UHD

  21. busy done 0 0 idle 0 1 finished 1 0 working 1 1 (undefined) Device Controller Interface . . . busy done Error code . . . Command Status Data 0 Data 1 Logic Data n-1 A. Berrached:CMS:UHD

  22. I/O Devices (cont.) • How does the computer communicate with an I/O device? • device controller has a set of registers: Command reg., Status reg., Dataregs., Address regs, etc. • Status reg.: tells the computer the status of device: idle, busy, non functional, etc. • A process can request an operation from device by placing a command in device’s Commandreg. • Data regs. Are used to exchange data • Address regs: used to indicate address of source/destination A. Berrached:CMS:UHD

  23. Performing a Write Operation while(deviceNo.busy || deviceNo.done) <waiting>; deviceNo.data[0] = <value to write> deviceNo.command = WRITE; while(deviceNo.busy) <waiting>; deviceNo.done = TRUE; • Devices much slower than CPU • CPU waits while device operates • Would like to multiplex CPU to a different process while I/O is in process A. Berrached:CMS:UHD

  24. … … … Ready Processes Ready Processes Ready Processes CPU CPU Device Device I/O Operation Uses CPU CPU-I/O Overlap CPU Device A. Berrached:CMS:UHD

  25. I/O Devices (cont.) • How does the computer operate on device controller registers? How does it identify each device? 1. Instruction set of the CPU may have special instructions to operate on I/O devices. E.g. Input DeviceN, DeviceRegisterN, Rn Output Rn, DeviceN, DeviceRegisterN etc. 2. Memory Mapped I/O A. Berrached:CMS:UHD

  26. Memory Mapped I/O • A set of memory addresses are reserved for I/O devices. E.g: 0000 to 3FF in Intel 8086 • each device is assigned a sub-set of memory addresses. • A memory address is assigned to each register of each device controller • regular CPU instructions are used to interact with device controller. A. Berrached:CMS:UHD

  27. I/O Devices (cont.) How does the CPU know when a device controller has completed the requested operation? • 1. Polling: CPU continually check status register of device controller • 2. Interrupt driven I/O: device controller sends a signal to CPU through the bus. • bus must support interrupts • CPU must include an interrupt flag • CPU instruction set must include instructions to test and set/clear interrupt flag. A. Berrached:CMS:UHD

  28. Determining When I/O is Complete CPU Interrupt Pending Device Device Device • CPU incorporates an “interrupt pending” flag • When device.busy  FALSE, interrupt pending flag is set • Hardware “tells” OS that the interrupt occurred • Interrupt handler part of the OS makes process ready to run A. Berrached:CMS:UHD

  29. Fetch-Execute Cycle with Interrupt PC = <Machine-Start-Address> ; IR = Memory[PC] ; haltFlag = CLEAR ; Decode(IR); while (haltFlag not SET) { Execute(IR); PC = PC + InstructionSize; if (InterruptFlag) { save current PC; // (e.g. in system stack) PC = AddressOfInterruptHandler; reset InterruptFlag; } IR = Memory[PC] ; Decode(IR); } A. Berrached:CMS:UHD

  30. Hardware Protection • Dual-Mode Operation • I/O Protection • Memory Protection A. Berrached:CMS:UHD

  31. Dual-Mode Operation • Sharing system resources requires that the operating system ensures a level of protection to the users: • an incorrect program can not cause other programs to execute incorrectly • that a user program cannot have access resource for it does not have permission • some operations should not be performed by user programs A. Berrached:CMS:UHD

  32. Dual-Mode Operation (Cont.) • Provide hardware support to differentiate between at least two modes of operations: 1. User mode - execution done on behalf of the user 2. Supervisor mode (also called monitor mode or privileged mode or protected mode or system mode etc.) - execution done on behalf of the operating system A. Berrached:CMS:UHD

  33. Dual-Mode Operation (Cont.) • Mode bit is added to computer hardware (to CPU) to indicate the current mode. Supervisor mode (0) user mode (1) • Instruction set: privileged instructions and non-privileged instructions - privileged instructions can be executed only in supervisor mode. • Operating system can execute any instruction. • Must insure that a user program can not execute privileged instructions directly. A. Berrached:CMS:UHD

  34. Going from User Mode to Supervisor Mode • When a user program need service from the OS (e.g. open a file, read, write, allocate memory etc.), it makes a system call: i.e. a call to one of the OS functions. • OS functions must run in supervisor mode. • User processes run in user mode. • computer designers had to come up with some kind of approach that would allow a user process to miraculously change the CPU mode to supervisor and branch to one of these OS functions simultaneously. The trap instruction is just the ticket. A. Berrached:CMS:UHD

  35. Trap Instruction • A trap instruction is a machine-level instruction that: • Switches the CPU mode to supervisor • Looks up the address of the target function in a kernel-space trap table • Branches to the entry point of the kernel-space function using the address from the trap table • The trick is that the instruction does all three of these steps rather than just one or two. And trap is the only instruction that sets the CPU mode bit to supervisor. A. Berrached:CMS:UHD

  36. The system call is translated into a trap instruction • the trap instruction is a machine level instruction that is part of the instruction set of the processor • The trap instruction will do the following: • change mode-bit to supervisor mode • jump to a trap handler which will determine which OS function is being requested etc. A. Berrached:CMS:UHD

  37. Dual-Mode Operation (Cont.) Processor must provide the following: • A Mode-bit flag • Instruction set: privileged instructions and non-privileged instructions • A trap instruction A. Berrached:CMS:UHD

  38. I/O protection • Instruction to change the mode must be privileged • I/O operation are privileged instructions • How can user program perform I/O? • It makes a system call to OS. • When a system call is made a trap instruction is executed: • sets the mode to supervisor mode • OS function verifies that parameters are correct and legal, executes the request, sets mode to user mode, and returns control to user program A. Berrached:CMS:UHD

  39. Memory Protection A. Berrached:CMS:UHD

  40. Example of Memory Protection A. Berrached:CMS:UHD

  41. Protection Hardware A. Berrached:CMS:UHD

More Related