Exceptional Control Flow: Exceptions and Processes

Similar documents
Today. Exceptional Control Flow Processes. Exceptions and Processes. Control Flow. Altering the Control Flow

Are branches/calls the only way we can get the processor to go somewhere in a program? What is a program? A processor? A process?

Today. Introduction to Computer Systems /18 243, Fall th Lecture. Control Flow. Altering the Control Flow.

Exceptional Control Flow Part I

Exceptional Control Flow Part I Oct. 17, 2002

Control Flow. Systemprogrammering 2007 Föreläsning 2 Exceptional Control Flow Part I. Exceptional Control Flow. Altering the Control Flow

Processes: Introduction. CS 241 February 13, 2012

Exceptional Control Flow Part I September 22, 2008

Giving credit where credit is due

Exceptional Control Flow Part I

Introduction to Computer Systems , fall th Lecture, Oct. 7 th

Excep&onal Control Flow: Excep&ons and Processes

Excep onal Control Flow: Excep ons and Processes

Processes, Exceptional

Processes. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

Carnegie Mellon. Processes. Lecture 12, May 19 th Alexandre David. Credits to Randy Bryant & Dave O Hallaron from Carnegie Mellon

OS Interaction and Processes

Exceptional Control Flow Part I Oct. 28, 2009"

CSE351 Inaugural Edi7on Spring

University of Washington What is a process?

Altering the Control Flow

Program and OS interac0ons: Excep0ons and Processes

Q & A (1) Where were string literals stored? Virtual Address. SSE2033: System Software Experiment 2 Spring 2016 Jin-Soo Kim

Announcement (1) sys.skku.edu is now available

Are branches/calls the only way we can get the processor to go somewhere in a program? What is a program? A processor? A process?

Altering the Control Flow

CSC 252: Computer Organization Spring 2018: Lecture 19

Exceptions, Processes and Signals

Exceptional Control Flow: Exceptions and Processes

Processes. CSE 351 Autumn Instructor: Justin Hsia

Processes. CSE 351 Autumn Instructor: Justin Hsia

Roadmap. Java: Assembly language: OS: Machine code: Computer system:

Exceptions and Processes

Approaches to Concurrency

Excep&onal+Control+Flow:++ Excep&ons+and+Processes+ + 15C213':'Introduc;on'to'Computer'Systems' 14 th 'Lecture,'Oct.'15,'2015'

Processes. CSE 351 Spring Instructor: Ruth Anderson

Foundations of Computer Systems

Foundations of Computer Systems

CS 201. Processes. Gerson Robboy Portland State University

Operating System. Chapter 3. Process. Lynn Choi School of Electrical Engineering

Excep&onal Control Flow: Excep&ons and Processes. (Chapter 8)

CS 201. Exceptions and Processes. Gerson Robboy Portland State University

Processes, Virtual Memory I

Virtual Memory I. CSE 351 Autumn Instructor: Justin Hsia

Systems Programming and Computer Architecture ( ) Timothy Roscoe

!"#$%&'()*+,'(-.'*+/*'01+!"#$%&'(2+)(3+4.'#$22$2

PROCESS PROGRAMMING INTERFACE

CS24: INTRODUCTION TO COMPUTING SYSTEMS. Spring 2018 Lecture 20

Exceptional Control Flow Part II Nov. 2, 2009"

CS213. Exceptional Control Flow Part II. Topics Process Hierarchy Signals

CS3733: Operating Systems

Processes & Signals. System Runs Many Processes Concurrently. State consists of memory image + register values + program counter

Lecture 24: Multitasking and Signals

Shell and Signals. Computer Organization 3/17/2015. CSC252 - Spring The World of Multiprogramming or Multitasking. Unix Process Hierarchy

Multitasking. Programmer s model of multitasking. fork() spawns new process. exit() terminates own process

Signals. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

Processes, Exceptional Control Flow

Giving credit where credit is due

Programming Assignments will be.. All the PAs are continuous 3 major factors that you should consider

Exceptional Control Flow Part II

Introduction to Unix. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

ECF Exists at All Levels of a System Exceptional Control Flow Part II Oct. 22, 2002 Topics! Process Hierarchy! Shells! Signals!

Operating Systems Components. What is an Operating System? Process Management. Memory Management. Operating Systems 9/7/2018 CSC 256/456 1

Exceptional Control Flow Exists at All Levels of a System. Systemprogrammering 2007 Föreläsning 3 Exceptional Control Flow Part II

Operating System Structure

Process Control. Philipp Koehn. 23 April 2018

Exceptions, Processes and Signals

CS 261 Fall Mike Lam, Professor. Exceptional Control Flow and Processes

Processes & Threads. (Chapter 3) CS 4410 Operating Systems. [R. Agarwal, L. Alvisi, A. Bracy, M. George, E. Sirer, R. Van Renesse]

Excep&onal Control Flow

CSCI2467: Systems Programming Concepts

CMPSCI 230 Computer Systems Principles. Processes

What is an Operating System? Signals, Processes, & Threads. Resource Sharing. Resource Abstraction ... Operating Systems 10/20/2010

Excep&onal Control Flow

Exceptional Control Flow: Signals and Nonlocal Jumps

System Programming. Process Control II

fork System-Level Function

CSC 1600 Unix Processes. Goals of This Lecture

CS24: INTRODUCTION TO COMPUTING SYSTEMS. Spring 2017 Lecture 19

Princeton University Computer Science 217: Introduction to Programming Systems. Process Management

Introduction to Processes

Princeton University Computer Science 217: Introduction to Programming Systems. Process Management

CS 475. Process = Address space + one thread of control Concurrent program = multiple threads of control

CSCB09: Software Tools and Systems Programming. Bianca Schroeder IC 460

Princeton University. Computer Science 217: Introduction to Programming Systems. Process Management

Processes. CS3026 Operating Systems Lecture 05

Process Management 1

CS 261 Fall Mike Lam, Professor. Processes

Lecture 4: Process Management

CS 355 Operating Systems. Keeping Track of Processes. When are processes created? Process States 1/26/18. Processes, Unix Processes and System Calls

Cache Example, System Control Flow

CS 31: Intro to Systems Processes. Kevin Webb Swarthmore College March 31, 2016

Processes & Threads. Today. Next Time. ! Process concept! Process model! Implementing processes! Multiprocessing once again. ! More of the same J

COE518 Lecture Notes Week 2 (Sept. 12, 2011)

CS240: Programming in C

CSci 4061 Introduction to Operating Systems. Processes in C/Unix

Last Class. System Calls, Kernel Mode, and Process Implementation. Processes. Today. Operating Systems 9/11/2018 CSC 256/456 1

518 Lecture Notes Week 3

Process Management. Outline. Process vs. Program. Address Space. How do we run a program? What are steps to create a process?

PROCESS CONTROL BLOCK TWO-STATE MODEL (CONT D)

Transcription:

Exceptional Control Flow: Exceptions and Processes 15-213 / 18-213: Introduction to Computer Systems 12 th Lecture, June 18, 2013 Instructors: Greg Kesden 1

Today Exceptional Control Flow Processes 2

Control Flow Processors do only one thing: From startup to shutdown, a CPU simply reads and executes (interprets) a sequence of instructions, one at a time This sequence is the CPU s control flow (or flow of control) Physical control flow Time <startup> inst 1 inst 2 inst 3 inst n <shutdown> 3

Altering the Control Flow Up to now: two mechanisms for changing control flow: Jumps and branches Call and return Both react to changes in program state Insufficient for a useful system: Difficult to react to changes in system state data arrives from a disk or a network adapter instruction divides by zero user hits Ctrl-C at the keyboard System timer expires System needs mechanisms for exceptional control flow 4

Exceptional Control Flow Exists at all levels of a computer system Low level mechanisms Exceptions change in control flow in response to a system event (i.e., change in system state) Combination of hardware and OS software Higher level mechanisms Process context switch Signals Nonlocal jumps: setjmp()/longjmp() Implemented by either: OS software (context switch and signals) C language runtime library (nonlocal jumps) What about try/catch/throw? 5

ECF Exists at All Levels of a System Exceptions Hardware and operating system kernel software Process Context Switch Hardware timer and kernel software Signals Kernel software and application software Nonlocal jumps Application code This Lecture Next Lecture 6

Exceptions An exception is a transfer of control to the OS in response to some event (i.e., change in processor state) User Process OS event I_current I_next exception return to I_current return to I_next abort exception processing by exception handler Examples: div by 0, arithmetic overflow, page fault, I/O request completes, Ctrl-C 7

Exception Tables Exception Table 0 1 2 n-1 Exception numbers... code for exception handler 0 code for exception handler 1 code for exception handler 2... Each type of event has a unique exception number k k = index into exception table (a.k.a. interrupt vector) almost Handler k is called each time exception k occurs code for exception handler n-1 8

Asynchronous Exceptions (Interrupts) Caused by events external to the processor Indicated by setting the processor s interrupt pin Handler returns to next instruction Examples: I/O interrupts hitting Ctrl-C at the keyboard arrival of a packet from a network arrival of data from a disk Hard reset interrupt hitting the reset button Soft reset interrupt hitting Ctrl-Alt-Delete on a PC 9

Synchronous Exceptions Caused by events that occur as a result of executing an instruction: Traps Intentional Examples: system calls, breakpoint traps, special instructions Returns control to next instruction Faults Unintentional but possibly recoverable Examples: page faults (recoverable), protection faults (unrecoverable), floating point exceptions Either re-executes faulting ( current ) instruction or aborts Aborts unintentional and unrecoverable Examples: parity error, machine check Aborts current program 10

Trap Example: Opening File User calls: open(filename, options) Function open executes system call instruction int 0804d070 < libc_open>:... 804d082: cd 80 int $0x80 804d084: 5b pop %ebx... User Process OS int pop exception returns open file Different privilege levels! OS must find or create file, get it ready for reading or writing Returns integer file descriptor 11

Fault Example: Page Fault User writes to memory location That portion (page) of user s memory is currently on disk int a[1000]; main () { a[500] = 13; 80483b7: c7 05 10 9d 04 08 0d movl $0xd,0x8049d10 User Process OS movl exception: page fault returns Create page and load into memory Page handler must load page into physical memory Returns to faulting instruction Successful on second try Different privilege levels! 12

Fault Example: Invalid Memory Reference int a[1000]; main () { a[5000] = 13; 80483b7: c7 05 60 e3 04 08 0d movl $0xd,0x804e360 User Process OS movl exception: page fault detect invalid address signal process Page handler detects invalid address Sends SIGSEGV signal to user process User process exits with segmentation fault Different privilege levels! 13

Exception Table IA32 (Excerpt) Exception Number Description Exception Class 0 Divide error Fault 13 General protection fault Fault 14 Page fault Fault 18 Machine check Abort 32-127 OS-defined Interrupt or trap 128 (0x80) System call Trap 129-255 OS-defined Interrupt or trap Check Table 6-1: http://download.intel.com/design/processor/manuals/253665.pdf 14

Altering the Control Flow (revisited) Up to now: two mechanisms for changing control flow: Jumps and branches Is there an alternative? Call and return Both react to changes in program state - For general purpose processors? - For embedded processors? Insufficient for a useful system: Difficult to react to changes in system state data arrives from a disk or a network adapter instruction divides by zero user hits Ctrl-C at the keyboard System timer expires System needs mechanisms for exceptional control flow 15

Today Exceptional Control Flow Processes 16

Processes Definition: A process is an instance of a running program. One of the most profound ideas in computer science Not the same as program or processor Process provides each program with two key abstractions: Logical control flow Each program seems to have exclusive use of the CPU Private virtual address space Each program seems to have exclusive use of main memory How are these Illusions maintained? Process executions interleaved (multitasking) or run on separate cores Address spaces managed by virtual memory system we ll talk about this in a couple of weeks 17

Concurrent Processes Two processes run concurrently (are concurrent) if their flows overlap in time Otherwise, they are sequential Examples (running on single core): Concurrent: A & B, A & C Sequential: B & C Process A Process B Process C Time 18

User View of Concurrent Processes Control flows for concurrent processes are physically disjoint in time However, we can think of concurrent processes as running in parallel with each other Time Process A Process B Process C 19

Context Switching Processes are managed by a shared chunk of OS code called the kernel Important: the kernel is not a separate process, but rather runs as part of some user process Control flow passes from one process to another via a context switch Process A Process B Time user code kernel code user code kernel code user code context switch context switch 20

fork: Creating New Processes int fork(void) creates a new process (child process) that is identical to the calling process (parent process) returns 0 to the child process returns child s pid (process id) to the parent process pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); Fork is interesting (and often confusing) because it is called once but returns twice 21

Understanding fork Process n pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); Child Process m pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid = m pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid = 0 pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); hello from parent Which one is first? hello from child 22

Fork Example #1 Parent and child both run same code Distinguish parent from child by return value from fork Start with same state, but each has private copy Including shared output file descriptor Relative ordering of their print statements undefined void fork1() { int x = 1; pid_t pid = fork(); if (pid == 0) { printf("child has x = %d\n", ++x); else { printf("parent has x = %d\n", --x); printf("bye from process %d with x = %d\n", getpid(), x); 23

Fork Example #2 Two consecutive forks void fork2() { printf("l0\n"); fork(); printf("l1\n"); fork(); printf("bye\n"); L1 L0 L1 Bye Bye Bye Bye 24

Fork Example #3 Three consecutive forks void fork3() { printf("l0\n"); fork(); printf("l1\n"); fork(); printf("l2\n"); fork(); printf("bye\n"); L1 L2 L0 L1 L2 L2 L2 Bye Bye Bye Bye Bye Bye Bye Bye 25

Fork Example #4 Nested forks in parent void fork4() { printf("l0\n"); if (fork()!= 0) { printf("l1\n"); if (fork()!= 0) { printf("l2\n"); fork(); printf("bye\n"); L0 L1 L2 Bye Bye Bye Bye 26

Fork Example #5 Nested forks in children void fork5() { printf("l0\n"); if (fork() == 0) { printf("l1\n"); if (fork() == 0) { printf("l2\n"); fork(); printf("bye\n ); L0 L2 L1 Bye Bye Bye Bye 27

exit: Ending a process void exit(int status) exits a process Normally return with status 0 atexit() registers functions to be executed upon exit void cleanup(void) { printf("cleaning up\n"); void fork6() { atexit(cleanup); fork(); exit(0); 28

Zombies Idea When process terminates, still consumes system resources Various tables maintained by OS Called a zombie Living corpse, half alive and half dead Reaping Performed by parent on terminated child (using wait or waitpid) Parent is given exit status information Kernel discards process What if parent doesn t reap? If any parent terminates without reaping a child, then child will be reaped by init process (pid == 1) So, only need explicit reaping in long-running processes e.g., shells and servers 29

Zombie Example linux>./forks 7 & [1] 6639 Running Parent, PID = 6639 Terminating Child, PID = 6640 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6639 ttyp9 00:00:03 forks 6640 ttyp9 00:00:00 forks <defunct> 6641 ttyp9 00:00:00 ps linux> void fork7() { if (fork() == 0) { /* Child */ printf("terminating Child, PID = %d\n", getpid()); exit(0); else { printf("running Parent, PID = %d\n", getpid()); while (1) ; /* Infinite loop */ ps shows child process as defunct 30

Zombie Example linux>./forks 7 & [1] 6639 Running Parent, PID = 6639 Terminating Child, PID = 6640 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6639 ttyp9 00:00:03 forks 6640 ttyp9 00:00:00 forks <defunct> 6641 ttyp9 00:00:00 ps linux> kill 6639 [1] Terminated linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6642 ttyp9 00:00:00 ps void fork7() { if (fork() == 0) { /* Child */ printf("terminating Child, PID = %d\n", getpid()); exit(0); else { printf("running Parent, PID = %d\n", getpid()); while (1) ; /* Infinite loop */ ps shows child process as defunct Killing parent allows child to be reaped by init 31

Nonterminating Child Example linux>./forks 8 Terminating Parent, PID = 6675 Running Child, PID = 6676 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6676 ttyp9 00:00:06 forks 6677 ttyp9 00:00:00 ps linux> void fork8() { if (fork() == 0) { /* Child */ printf("running Child, PID = %d\n", getpid()); while (1) ; /* Infinite loop */ else { printf("terminating Parent, PID = %d\n", getpid()); exit(0); Child process still active even though parent has terminated 32

Nonterminating Child Example linux>./forks 8 Terminating Parent, PID = 6675 Running Child, PID = 6676 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6676 ttyp9 00:00:06 forks 6677 ttyp9 00:00:00 ps linux> kill 6676 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6678 ttyp9 00:00:00 ps void fork8() { if (fork() == 0) { /* Child */ printf("running Child, PID = %d\n", getpid()); while (1) ; /* Infinite loop */ else { printf("terminating Parent, PID = %d\n", getpid()); exit(0); Child process still active even though parent has terminated Must kill explicitly, or else will keep running indefinitely 33

wait: Synchronizing with Children Parent reaps child by calling the wait function int wait(int *child_status) suspends current process until one of its children terminates return value is the pid of the child process that terminated if child_status!= NULL, then the object it points to will be set to a status indicating why the child process terminated 34

wait: Synchronizing with Children void fork9() { int child_status; if (fork() == 0) { printf("hc: hello from child\n"); else { printf("hp: hello from parent\n"); wait(&child_status); printf("ct: child has terminated\n"); printf("bye\n"); exit(); HC Bye HP CT Bye 35

wait() Example If multiple children completed, will take in arbitrary order Can use macros WIFEXITED and WEXITSTATUS to get information about exit status void fork10() { pid_t pid[n]; int i; int child_status; for (i = 0; i < N; i++) if ((pid[i] = fork()) == 0) exit(100+i); /* Child */ for (i = 0; i < N; i++) { pid_t wpid = wait(&child_status); if (WIFEXITED(child_status)) printf("child %d terminated with exit status %d\n", wpid, WEXITSTATUS(child_status)); else printf("child %d terminate abnormally\n", wpid); 36

waitpid(): Waiting for a Specific Process waitpid(pid, &status, options) suspends current process until specific process terminates various options (see textbook) void fork11() { pid_t pid[n]; int i; int child_status; for (i = 0; i < N; i++) if ((pid[i] = fork()) == 0) exit(100+i); /* Child */ for (i = N-1; i >= 0; i--) { pid_t wpid = waitpid(pid[i], &child_status, 0); if (WIFEXITED(child_status)) printf("child %d terminated with exit status %d\n", wpid, WEXITSTATUS(child_status)); else printf("child %d terminated abnormally\n", wpid); 37

execve: Loading and Running Programs int execve( char *filename, char *argv[], char *envp[] ) Loads and runs in current process: Executable filename With argument list argv And environment variable list envp Does not return (unless error) Overwrites code, data, and stack keeps pid, open files and signal context Environment variables: name=value strings getenv and putenv Null-terminated env var strings Null-terminated cmd line arg strings unused envp[n] == NULL envp[n-1] envp[0] argv[argc] == NULL argv[argc-1] argv[0] Linker vars envp argv argc Stack frame for main Carnegie Mellon Stack bottom Stack top environ 38

execve Example if ((pid = Fork()) == 0) { /* Child runs user job */ if (execve(argv[0], argv, environ) < 0) { printf("%s: Command not found.\n", argv[0]); exit(0); argv argv[argc] = NULL argv[argc-1] argv[0] /usr/include -lt ls environ envp[n] = NULL envp[n-1] envp[0] PWD=/usr/droh PRINTER=iron USER=droh 39

Summary Exceptions Events that require nonstandard control flow Generated externally (interrupts) or internally (traps and faults) Processes At any given time, system has multiple active processes Only one can execute at a time on a single core, though Each process appears to have total control of processor + private memory space 40

Summary (cont.) Spawning processes Call fork One call, two returns Process completion Call exit One call, no return Reaping and waiting for processes Call wait or waitpid Loading and running programs Call execve (or variant) One call, (normally) no return 41