Scribd
Upload
62 views25 pages

Untitled

This lecture covered hardware protection mechanisms, operating system components and services, system calls, and OS structures. Hardware protection includes dual-mode operation, I/O protection using privileged instructions, memory protection using base and limit registers, and CPU protection with timers. OS components manage processes, memory, storage, I/O, files, networking and more. Services include program execution, I/O, file access, and communication. System calls allow user processes secure access to OS resources through an interface layer. Common OS structures include layered and modular designs.

Uploaded by

ASFAR ALI
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
62 views25 pages

Untitled

This lecture covered hardware protection mechanisms, operating system components and services, system calls, and OS structures. Hardware protection includes dual-mode operation, I/O protection using privileged instructions, memory protection using base and limit registers, and CPU protection with timers. OS components manage processes, memory, storage, I/O, files, networking and more. Services include program execution, I/O, file access, and communication. System calls allow user processes secure access to OS resources through an interface layer. Common OS structures include layered and modular designs.

Uploaded by

ASFAR ALI
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 25

Lecture 3

Agenda for Today


 Review of previous lecture
 Hardware (I/O, memory, and CPU)
protection
 Operating system components and
services
 System calls

 Operating system structures

 Operating system design and


implementation
 Recap of the lecture
2
Hardware Protection
 Dual-Mode Operation
 I/O Protection
 Memory Protection
 CPU Protection

3
I/O Protection
 All I/O instructions are privileged
instructions.
 Must ensure that a user program could
never gain control of the computer in
monitor mode (i.e., a user program
that, as part of its execution, stores a
new address in the interrupt vector).

4
Use of A System Call to
Perform I/O

5
 Must provide memory protection outside the
address space of a process.
 In order to have memory protection, add two
registers that determine the range of legal
addresses a program may access:
 Base register – holds the smallest legal physical
memory address.
 Limit register – contains the size of the range
 Memory outside the defined range is protected.

6
7
8
 Timer – interrupts computer after specified
period to ensure operating system maintains
control.
 Timer is decremented every clock tick.
 When timer reaches the value 0, an interrupt occurs.
 Timer commonly used to implement time
sharing.
 Time also used to compute the current time.
 Load-timer is a privileged instruction.

9
OS Components
 Process management
 Main memory management
 Secondary storage management
 I/O system management
 File management
 Protection system
 Networking
 Command-line interpreter (shells)
10
Services for user and users of
programs:
 Program execution
 I/O Operations
 File System Manipulation
 Communications between
processes/users
 Error detection and handling
Services for efficient system operation:
 Resource management
 Accounting
 Protection
Users
Applications
Operating System API, AUI
Operating System Kernel
Computer Hardware
Real work is done in the kernel
System Call Signal

Interrupt Trap
 User processes must not be given
open access to the kernel code
 The system call interface layer
contains entry point in the kernel
code
 Any user or application request that
involves access to any system
resource must be handled by the
kernel code
 Process Control
 File Management
 Device Management
 Information maintenance
 Communications
 The user program makes a call to a library
function.
 Library routine puts appropriate parameters at a
well-known place (registers, stack, or a table in
memory).
 The trap instruction is executed to change
mode from user to kernel.
 Control goes to operating system.
 Operating system determines which system call
is to be carried out.
 Kernel indexes the dispatch table, which
contains pointers to service routines for system
calls.
 Service routine is executed and return
parameter or error code placed at well-known
places (usually a CPU register).
 Control given back to user program.
 Library function executes the instruction
following trap.
Process

Library Call

System Call

trap

Dispatch Table
Service
Code
Kernel
Code
 Simple Structure
 Layered Approach
 Microkernels
 Virtual Machines
MS-DOS : written to provide the most functionality in the
least space, so it was not divided into modules carefully
 UNIX consists of two separable parts,
the kernel and the system programs.
 Every thing below the system call
interface and above the physical
hardware is the kernel.
 An enormous amount of
functionality combined in one level,
UNIX is difficult to enhance as
changes in one section could
adversely affect other areas.
Recap of lecture
 Review of previous lecture
 Operating system components
 Operating system services
 System calls
 Operating system structures
 Recap of the lecture

24
Operating Systems

Lecture 3

25

You might also like