1 P3, P4 Dave Eckhardt 1 Outline ● P3 grading approach ● Coping with P3 disasters ● P4.

Slides:



Advertisements
Similar presentations
Installing DOS and Windows98 under MS Virtual PC.
Advertisements

CSC 360- Instructor: K. Wu Overview of Operating Systems.
Operating System.
Operating Systems Manage system resources –CPU scheduling –Process management –Memory management –Input/Output device management –Storage device management.
Nummenmaa & Thanish: Practical Distributed Commit in Modern Environments PDCS’01 PRACTICAL DISTRIBUTED COMMIT IN MODERN ENVIRONMENTS by Jyrki Nummenmaa.
CSC 501 Lecture 2: Processes. Von Neumann Model Both program and data reside in memory Execution stages in CPU: Fetch instruction Decode instruction Execute.
Operating Systems High Level View Chapter 1,2. Who is the User? End Users Application Programmers System Programmers Administrators.
Processes CSCI 444/544 Operating Systems Fall 2008.
Unit 6- Operating Systems.  Identify the purpose of an OS  Identify different operating systems  Describe computer user interaction with multiple operating.
OS Fall ’ 02 Introduction Operating Systems Fall 2002.
IT Systems Operating System EN230-1 Justin Champion C208 –
1 CS 333 Introduction to Operating Systems Class 2 – OS-Related Hardware & Software The Process Concept Jonathan Walpole Computer Science Portland State.
CS 300 – Lecture 22 Intro to Computer Architecture / Assembly Language Virtual Memory.
Introduction to Kernel
OS Spring’03 Introduction Operating Systems Spring 2003.
1 Project 2 Dave Eckhardt 1 Synchronization ● P2 (et seq.) partners – “Partner Registration Page” on web site!! ● Good things to.
Introduction Operating Systems’ Concepts and Structure Lecture 1 ~ Spring, 2008 ~ Spring, 2008TUCN. Operating Systems. Lecture 1.
Build an Operating System
Threads CS 416: Operating Systems Design, Spring 2001 Department of Computer Science Rutgers University
Operating Systems (CSCI2413) Lecture 3 Processes phones off (please)
OS Spring’04 Introduction Operating Systems Spring 2004.
Operating System Organization
Processes in Unix, Linux, and Windows CS-502 Fall Processes in Unix, Linux, and Windows CS502 Operating Systems (Slides include materials from Operating.
Lecture 1 Page 1 CS 111 Summer 2015 Introduction CS 111 Operating System Principles.
CSC 501 Lecture 2: Processes. Process Process is a running program a program in execution an “instantiation” of a program Program is a bunch of instructions.
1 Boot Camp Dave Eckhardt 1 This Is a Hard Class ● Traditional hazards – 410 letter grade one lower than other classes – All other.
Computing and the Web Operating Systems. Overview n What is an Operating System n Booting the Computer n User Interfaces n Files and File Management n.
Processes and OS basics. RHS – SOC 2 OS Basics An Operating System (OS) is essentially an abstraction of a computer As a user or programmer, I do not.
Computer Architecture and Operating Systems CS 3230: Operating System Section Lecture OS-1 Process Concepts Department of Computer Science and Software.
Lecture 3 Process Concepts. What is a Process? A process is the dynamic execution context of an executing program. Several processes may run concurrently,
Background: Operating Systems Brad Karp UCL Computer Science CS GZ03 / M th November, 2008.
Lecture 1 Page 1 CS 111 Summer 2013 Introduction CS 111 Operating System Principles Peter Reiher.
OPERATING SYSTEM - program that is loaded into the computer and coordinates all the activities among computer hardware devices. -controls the hardware.
Computer Systems Week 14: Memory Management Amanda Oddie.
1 CSE451 Architectural Supports for Operating Systems Autumn 2002 Gary Kimura Lecture #2 October 2, 2002.
Bootstrapping Steve Muckle Dave Eckhardt. Carnegie Mellon University1 Synchronization Project 3 checkpoint 1 Bboard post, web page Paging, COW optional.
1 Introduction to Dave Eckhardt
CS140 Project 1: Threads Slides by Kiyoshi Shikuma.
1 Computer Systems II Introduction to Processes. 2 First Two Major Computer System Evolution Steps Led to the idea of multiprogramming (multiple concurrent.
(a) What is the output generated by this program? In fact the output is not uniquely defined, i.e., it is not necessarily the same in each execution. What.
15-410, S’ The Process Jan. 21, 2004 Dave Eckhardt Bruce Maggs L05_Process “System call abuse for fun & profit”
Lecture 26 Virtual Machine Monitors. Virtual Machines Goal: run an guest OS over an host OS Who has done this? Why might it be useful? Examples: Vmware,
Genesis: From Raw Hardware to Processes Andy Wang Operating Systems COP 4610 / CGS 5765.
Project 2: User Programs Abdelmounaam Rezgui Acknowledgment: The content of some slides is partly taken from Josh Wiseman’s presentation.
1 Exam Feedback Dave Eckhardt
1 The Process Dave Eckhardt 1 Synchronization ● Exam flavor? – Is 50 minutes enough? – Two mid-terms? Evening exam? ● Concurrency.
1 Feedback Dave Eckhardt 1 Homework Q2 ● Was deadlock prevention an option for P2? ● Answer – We couldn't violate the “mutual exclusion”
U NIVERSITY OF M ASSACHUSETTS, A MHERST Department of Computer Science Emery Berger University of Massachusetts, Amherst Operating Systems CMPSCI 377 Lecture.
Concepts and Structures. Main difficulties with OS design synchronization ensure a program waiting for an I/O device receives the signal mutual exclusion.
Lecture 4 Page 1 CS 111 Online Modularity and Memory Clearly, programs must have access to memory We need abstractions that give them the required access.
24/06/20161 Hardware Processor components & ROM. 224/06/2016 Learning Objectives Describe the function and purpose of the control unit, memory unit and.
Introduction to Kernel
Introduction to Operating Systems
CS 6560: Operating Systems Design
Modeling Page Replacement Algorithms
Lecture 24 Virtual Machine Monitors
CS 3305 System Calls Lecture 7.
Lecture 1 Runtime environments.
Modularity and Memory Clearly, programs must have access to memory
ICS Principles of Operating Systems
More examples How many processes does this piece of code create?
Modeling Page Replacement Algorithms
Lecture Topics: 11/1 General Operating System Concepts Processes
Threads and Concurrency
Modern PC operating systems
Lecture 6: Multiprogramming and Context Switching
Processes David Ferry CSCI 3500 – Operating Systems
Processes and Process Table
CSE 153 Design of Operating Systems Winter 2019
Presentation transcript:

1 P3, P4 Dave Eckhardt

1 Outline ● P3 grading approach ● Coping with P3 disasters ● P4

1 P3 Grading Approach ● Substantially according to “Plan of Attack” ● Key milestone: does the shell run? – virtual memory, system call boundary, context switch – fork(), exec() – wait(), exit() – readline() [basic] – Functional, if limited, maybe-unstable, OS

1 P3 Grading Approach ● Semi-automatic test environment – Kernel booted – Shell calls “magic” readline – Simics used to simulate command line – Single test runs – Second call to readline shuts down kernel

1 Approximate Breakdown

1 P3 Disasters? ● Some groups seem not “done” – One or more conceptual problems – Time management issues – Merge failures – “Out of gas”

1 P3 Disasters ● P3 is central to this class – Pedagogically, you should finish it – Very difficult to do a kernel extension (P4) w/o P3 – Potential exam trouble ● Some people have asked about withdrawing ● I'd prefer finishing to withdrawing...

1 What I Can Offer ● An additional week – We do need to grade these... ● Including interviews ● The bad news... – This extra P3 time will preclude P4 ● How to decide? – Educational goal: understanding core principles – “Hurdle” model

1 P3 Hurdle ● Test suite to be released around midnight – After “P3 clock” has run out for 3-late-day groups – Basic tests – essentially what was already released – Solidity tests – subset of grading suite ● “Self-grade” by running them yourselves ● If you pass, register on “P4 registration page” ● Otherwise – P4 grade = 0%; late P3 may end up with mild penalty

1 Moving Forward ● Read your partner's code – Regardless of whether you made the deadline! – You need to understand the whole thing ● Even if time constraints mean you can't write your own ● Think about what happened – Maybe write down what you will do differently ● Plan time wisely –...based on your painfully-won self-knowledge

1 P4 Projects ● Paging – we will provide IDE disk driver ● File system – Read-only is ok – Simplified format ok (e.g., FAT) – One option: turn “executable RAM disk” into r/o fs ● Console extensions – Multiple virtual consoles, hot-key swap – “System monitor” line at bottom of display

1 Icing on the cake? ● Try your kernel on real hardware – So you can amaze your friends & family ● Not unusual for there to be some glitch – Uninitialized variable ● Real PC may have different RAM contents than simics PC – Clock interrupt happens too early

1 Lecture Topic Survey (Pick 3?) ● Remote file systems ● Distributed time & agreement ● Exotic operating system designs ● Naming in the Internet ● Mobile code ● Transactions ● PGP key-signing party?