DOCSLIB.ORG

Interrupt Handler Μ−Kernel – Harder to Let System Services Share Resources Dispatcher • Why?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Interrupt Handler Μ−Kernel – Harder to Let System Services Share Resources Dispatcher • Why? Operating System “Structures” Otto J. Anshus 1 Demo •POS P5 (today) •MorbOS (tomorrow) 2 “Structures” (Architectures) • Layered • OS as Resource Manager & Protector • Monolithic – HW (CPU, memory, ...) – SW (file systems, network stack, ...) • Micro kernel – Isolate users and processes from each other • OS as illusionist (a.k.a. virtual machine) • Virtual Machine – Abstractions – Easy use of abstractions • Unix: read/write data from/to sockets instead of having to • Hybrids handle TCP/IP packets in user level code 3 Layered • Hiding information at each layer • Develop a layer at a time Level N • Examples . – THE (6 layers, semaphores, Dijkstra 1968) . – MS-DOS (4 layers) Level 2 • Pros – Separation of concerns Level 1 – Elegant (at first sight) • Cons Hardware – Protection boundary crossings – Performance 4 Layered • Hiding information at each layer • Develop a layer at a time Level N • Examples . – THE (6 layers, semaphores, Dijkstra 1968) . – MS-DOS (4 layers) Level 2 • Pros – Separation of concerns Level 1 – Elegant (at first sight) • Cons Hardware – Protection boundary crossings – Performance Each layer can end up having to support multiple events happening (a.k.a. complications (and we don’t like complications)) 4 Layered • Hiding information at each layer • Develop a layer at a time Level N • Examples . B – THE (6 layers, semaphores, Dijkstra 1968) . A – MS-DOS (4 layers) Level 2 D • Pros – Separation of concerns Level 1 – Elegant (at first sight) • Cons Hardware – Protection boundary crossings – Performance Each layer can end up having to support multiple events happening (a.k.a. complications (and we don’t like complications)) 4 Monolithic • All of OS is in a fat Kernel User User • Examples program program – Classic Unix (Linux, BSD Unix, ...) return – Windows NT (hybrid) call – Mach (can be a fat kernel) – MacOS (Mach kernel) • Pro entry – Performance – Shared kernel space Kernel (Does it all) • Cons – Stability: Faulty drivers can crash the system (>75% of a modern OS are drivers). – Flexibility: Low • (However, made flexible with loadable kernel modules (Linux)) – Security • All runs in privileged kernel mode, with direct access to kernel data structures. • Kernel allow module loading (Great for a rootkit.) 5 Microkernel • Micro-kernel has just a few abstractions and functionalities – Abstractions • Process abstraction, address space, interrupts, IPC User OS – Syscall & very few services process Services • OS Services are implemented as user level processes return • Micro-kernel gets services on behalf of users by messaging call message with the service processes passing • Old – Nucleus, Taos, Mach (as a micro kernel, drivers still in entry kernel), • Newer µ−kernel – Minix (Andy Tanenbaum, VU) – Singularity (MS Research) Mach: The mother of all microkernels, 1985-1994. Rick – EROS/CoyotOS (Johns Hopkins University) Rashid (CMU, Microsoft Research), Avie Tevanian (ex-Apple CTO), Brian Bershad (U of Washington, Google) – L4 microkernel family (originally Jochen Liedtke when at IBM/GMD/Karlsruhe) Single Server Unix (BSD4.3) MkLinux (OSF) Brinch-Hansen: “The Nucleus of a Multiprogramming IBM Workplace OS 6 System..”, 1970. Recommended readings. NeXT OS -> Mac OS X Microkernel Pros et Cons • Pros – Smaller kernel User OS • Less bugs • Easier to tune/optimize process Services • Easier to port to a new platform return – Extend or customize call – Do verification – Trust (TCB) – Fault isolation entry • Cons Interrupt handler µ−kernel – Harder to let system services share resources Dispatcher • Why? 7 Microkernel Pros et Cons • Pros – Smaller kernel User OS • Less bugs • Easier to tune/optimize process Services • Easier to port to a new platform return – Extend or customize call – Do verification – Trust (TCB) – Fault isolation entry • Cons Interrupt handler µ−kernel – Harder to let system services share resources Dispatcher • Why? – Performance • Naive case: Multiple protection boundary crossings – How many? 7 Microkernel Pros et Cons • Pros – Smaller kernel User OS • Less bugs • Easier to tune/optimize process Services • Easier to port to a new platform return – Extend or customize call – Do verification – Trust (TCB) – Fault isolation entry • Cons Interrupt handler µ−kernel – Harder to let system services share resources Dispatcher • Why? – Performance • Naive case: Multiple protection boundary crossings – How many? 7 Microkernel Pros et Cons • Pros – Smaller kernel User OS • Less bugs • Easier to tune/optimize process Services • Easier to port to a new platform return – Extend or customize call – Do verification – Trust (TCB) – Fault isolation entry • Cons Interrupt handler µ−kernel – Harder to let system services share resources Dispatcher • Why? – Performance • Naive case: Multiple protection boundary crossings – How many? 7 Microkernel Pros et Cons • Pros – Smaller kernel User OS • Less bugs • Easier to tune/optimize process Services • Easier to port to a new platform return – Extend or customize call – Do verification – Trust (TCB) – Fault isolation entry • Cons Interrupt handler µ−kernel – Harder to let system services share resources Dispatcher • Why? – Performance • Naive case: Multiple protection boundary crossings – How many? 7 Microkernel Pros et Cons • Pros – Smaller kernel User OS • Less bugs • Easier to tune/optimize process Services • Easier to port to a new platform return – Extend or customize call – Do verification – Trust (TCB) – Fault isolation entry • Cons Interrupt handler µ−kernel – Harder to let system services share resources Dispatcher • Why? – Performance • Naive case: Multiple protection boundary crossings – How many? 7 User User process process Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service let Service run || OSK continue Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; Get parameters and Start requested service Service let Service run || OSK continue Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware ALTERNATIVELY: Sometimes later int 80h (when Service finishes) {K||service||processes} int by HW Interrupts from network, disk, keyboard,… User User process process Call Service(…); int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; make UL caller of Service Ready again AND write results to UL memory Get parameters and Start requested service Service let Service run || OSK continue Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware ALTERNATIVELY: Sometimes later int 80h (when Service finishes) {K||service||processes} int by HW Interrupts from network, disk, keyboard,… User User Service process process Service Call Service(…); Service Service int 80h Operating System Kernel INTERRUPT HANDLER: Analyze interrupt; make UL caller of Service Ready again AND write results to UL memory Get parameters and Start requested service Service let Service run || OSK continue Service int 8016 Service SCHEDULER: Select next process to resume DISPATCHER: restore context and iret Interrupt Hardware ALTERNATIVELY: Sometimes later int 80h (when Service finishes) {K||service||processes} int by HW Interrupts from network, disk, keyboard,… User User Service process process Service Call Service(…); Service Service int 80h Operating System
Load more

Recommended publications
  • Ebook - Informations About Operating Systems Version: August 15, 2006 | Download
    eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org AIX Internet: AIX AmigaOS Internet: AmigaOS AtheOS Internet: AtheOS BeIA Internet: BeIA BeOS Internet: BeOS BSDi Internet: BSDi CP/M Internet: CP/M Darwin Internet: Darwin EPOC Internet: EPOC FreeBSD Internet: FreeBSD HP-UX Internet: HP-UX Hurd Internet: Hurd Inferno Internet: Inferno IRIX Internet: IRIX JavaOS Internet: JavaOS LFS Internet: LFS Linspire Internet: Linspire Linux Internet: Linux MacOS Internet: MacOS Minix Internet: Minix MorphOS Internet: MorphOS MS-DOS Internet: MS-DOS MVS Internet: MVS NetBSD Internet: NetBSD NetWare Internet: NetWare Newdeal Internet: Newdeal NEXTSTEP Internet: NEXTSTEP OpenBSD Internet: OpenBSD OS/2 Internet: OS/2 Further operating systems Internet: Further operating systems PalmOS Internet: PalmOS Plan9 Internet: Plan9 QNX Internet: QNX RiscOS Internet: RiscOS Solaris Internet: Solaris SuSE Linux Internet: SuSE Linux Unicos Internet: Unicos Unix Internet: Unix Unixware Internet: Unixware Windows 2000 Internet: Windows 2000 Windows 3.11 Internet: Windows 3.11 Windows 95 Internet: Windows 95 Windows 98 Internet: Windows 98 Windows CE Internet: Windows CE Windows Family Internet: Windows Family Windows ME Internet: Windows ME Seite 1 von 138 eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org Windows NT 3.1 Internet: Windows NT 3.1 Windows NT 4.0 Internet: Windows NT 4.0 Windows Server 2003 Internet: Windows Server 2003 Windows Vista Internet: Windows Vista Windows XP Internet: Windows XP Apple - Company Internet: Apple - Company AT&T - Company Internet: AT&T - Company Be Inc. - Company Internet: Be Inc. - Company BSD Family Internet: BSD Family Cray Inc.
    [Show full text]
  • Occupational Health and Safety Risks in the Healthcare Sector
    Occupational health and safety risks in the healthcare sector Guide to prevention and good practice This publication is supported by the European Union Programme for Employment and Social Solidarity - PROGRESS (2007-2013). This programme is implemented by the European Commission. It was established to financially support the implementation of the objectives of the European Union in the employment, social affairs and equal oppor- tunities area, and thereby contribute to the achievement of the Europe 2020 Strategy goals in these fields. The seven-year Programme targets all stakeholders who can help shape the development of appropriate and effective employment and social legislation and policies, across the EU-27, EFTA-EEA and EU candidate and pre-candidate countries. For more information see: http://ec.europa.eu/progress Occupational health and safety risks in the healthcare sector European Commission Directorate-General for Employment, Social Affairs and Inclusion Unit B.3 Manuscript completed in December 2010 Neither the European Commission nor any person acting on behalf of the Commission may be held responsible for the use that may be made of the information contained in this publication. © Cover photos: iStock For any use or reproduction of photos which are not under European Union copyright, permission must be sought directly from the copyright holder(s). This guide has been produced by the Bundesanstalt für Arbeitsschutz und Arbeitsmedizin (BAuA), Berufsgenossenschaft für Gesundheitsdienst und Wohlfahrtspflege (BGW), contec Gesellschaft für Organisationsentwicklung mbH, Deutsches Netz Gesundheitsfördernder Krankenhäuser (DNGfK) and BAD/ Team Prevent GmbH. Europe Direct is a service to help you find answers to your questions about the European Union Freephone number (*): 00 800 6 7 8 9 10 11 (*) Certain mobile telephone operators do not allow access to 00 800 numbers or these calls may be billed.
    [Show full text]
  • Rights Reserved. Permission to Make Digital Or Hard Copies of All Or Part Of
    Copyright © 1994, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 Microsoft Windows NT And The Competition for Desktop Computing January 1994 Department ofElectrical Engineering and Computer Sciences University ofCalifornia Berkeley, California 94720 Abstract This report contains two papers, An Introduction to Microsoft Windows NT And Its Competitors, and The Status ofWindows NT and Its Competitors At The End of1993. The first paper, written in April 1993,presents an overview of the technology of Windows NT, and analyzes the competitors and competitive factors in the desktop operating system race.
    [Show full text]
  • All Computer Applications Need to Store and Retrieve Information
    MyFS: An Enhanced File System for MINIX A Dissertation Submitted in partial fulfillment of the requirement for the award of the degree of MASTER OF ENGINEERING ( COMPUTER TECHNOLOGY & APPLICATIONS ) By ASHISH BHAWSAR College Roll No. 05/CTA/03 Delhi University Roll No. 3005 Under the guidance of Prof. Asok De Department Of Computer Engineering Delhi College Of Engineering, New Delhi-110042 (University of Delhi) July-2005 1 CERTIFICATE This is to certify that the dissertation entitled “MyFS: An Enhanced File System for MINIX” submitted by Ashish Bhawsar in the partial fulfillment of the requirement for the award of degree of Master of Engineering in Computer Technology and Application, Delhi College of Engineering is an account of his work carried out under my guidance and supervision. Professor D. Roy Choudhury Professor Asok De Head of Department Head of Department Department of Computer Engineering Department of Information Technology Delhi College of Engineering Delhi College of Engineering Delhi Delhi 2 ACKNOWLEDGEMENT It is a great pleasure to have the opportunity to extent my heartiest felt gratitude to everybody who helped me throughout the course of this project. I would like to express my heartiest felt regards to Dr. Asok De, Head of the Department, Department of Information Technology for the constant motivation and support during the duration of this project. It is my privilege and owner to have worked under the supervision. His invaluable guidance and helpful discussions in every stage of this thesis really helped me in materializing this project. It is indeed difficult to put his contribution in few words. I would also like to take this opportunity to present my most sincere regards to Dr.
    [Show full text]
  • Microkernel Construction Introduction
    Microkernel Construction Introduction Nils Asmussen 04/09/2020 1 / 32 Normal Organization Thursday, 4th DS, 2 SWS Slides: www.tudos.org ! Studies ! Lectures ! MKC Subscribe to our mailing list: www.tudos.org/mailman/listinfo/mkc2020 In winter term: Microkernel-based operating systems (MOS) Various labs 2 / 32 Organization due to COVID-19 Slides and video recordings of lectures will be published Questions can be asked on the mailing list Subscribe to the mailing list! Practical exercises are planed for the end of the semester Depending on how COVID-19 continues, exercises are in person or we use some video-conferencing tool 3 / 32 Goals 1 Provide deeper understanding of OS mechanisms 2 Look at the implementation details of microkernels 3 Make you become enthusiastic microkernel hackers 4 Propaganda for OS research done at TU Dresden and Barkhausen Institut 4 / 32 Outline Organization Monolithic vs. Microkernel Kernel design comparison Examples for microkernel-based systems Vision vs. Reality Challenges Overview About L4/NOVA 5 / 32 Monolithic Kernel System Design u s Application Application Application e r k Kernel e r File Network n e Systems Stacks l m Memory Process o Drivers Management Management d e Hardware 6 / 32 Monolithic Kernel OS (Propaganda) System components run in privileged mode No protection between system components Faulty driver can crash the whole system Malicious app could exploit bug in faulty driver More than 2=3 of today's OS code are drivers No need for good system design Direct access to data structures Undocumented
    [Show full text]
  • Integrated Report 2019
    Integrated Report 2019 JP TOWER, 2-7-2 Marunouchi, Chiyoda-ku, Tokyo 100-7015, Japan Phone: +81-3-6250-2111 https://konicaminolta.com CONTENTS On the Release of Integrated Report 2019 1 On the Release of Integrated Report 2019 2 CONTENTS Konica Minolta’s Strengths 03 Since fiscal 2015, Konica Minolta has released annual reports (the name of these reports was changed to the and Value Creation 3 Konica Minolta Philosophy integrated report in 2017) that provide a comprehensive look at the Company's activities and philosophies. 7 Value Creation Process The fifth report is now available. We made this integrated report to be a communication tool to better 9 Konica Minolta's Strengths 1. Customer base familiarize stakeholders, including shareholders and investors, with Konica Minolta by systematically 11 Konica Minolta’s Strengths 2. Technical expertise organizing both financial and non-financial information. 13 Konica Minolta’s Strengths 3. Business Model The 2018 integrated report was externally well-received, winning recognition and awards that included Growth Strategy 15 the Special Award in the Nikkei Annual Report Awards conducted by Nikkei Inc., and the Excellence in 15 Medium Term Business Plan Integrated Reporting Prize at the 6th WICI Japan Awards for Excellence in Integrated Reporting. 17 Message from the CEO Integrated Report 2019 clarifies the Konica Minolta Group's strengths and value creation processes 25 Message from the CFO 29 while explaining the Group's medium- to long-term business strategy and pathway to value creation with a Special Topics Building High Value-Added Businesses focus on SHINKA 2019, the new Medium Term Business Plan formulated in 2017.
    [Show full text]
  • This Is a Fairy Tale •.• NOT! a Primer on Moving SAS® Applications
    This is a Fairy Tale•.• NOT! A Primer on Moving SAS® Applications Across Graphical Operating Systems James Hefner, Entergy Corporation, Beaumont, TX lineup. The PowerPC's PowerOpen operating system should be ABSTRACT able to run Windows, Windows NT, OS/2, Macintosh, and UNIX applications unmodified (using SoftPC to run Windows & OS/2 Currently, most SAS Software application developers have on~ apps). Current plans are to offer these new machines at prices one or two graphical operating systems (such as Microsoft that are highly competitive with the current top-of-the-!ine WindowsTN, or OSFlMoti~ to support. However, the pending offerings by IBM PC manufacturerS and Apple, nol 10 mention release of the SAS System for the Apple® Macintosh®I and the UNIX workstations. This could mean a change in the platform you introduction of new hardware and software such as the PowerPC are currently using, as well as the ability (or need) to be able to and Wabi, means that application developers may have to use and write applications using any of the five operating support two or more graphical operating systems. systems. This paper is intended to assist application developers, both in New Graphical Operating Systems the teaching of the fundamentals of graphical operating systems, and in Ihe moving of SAS/Af® and SAS/EIS® applicalions from In addition to the platforms mentioned above, Apple and IBM are one operating system to another. currently working on the Taligent operating system, which will have an object-oriented, graphical front end. IBM is also INTRODUCTION discussing porling its object·orienled 0512 2.x Workplace Shell 10 a new ver.sion of PC DOS® and AIX®, IBM's version of UNIX (to If you are a SAS' application developer, you may currently be be called Workplace OS).
    [Show full text]
  • Flexible Task Management for Self-Adaptation of Mixed-Criticality Systems with an Automotive Example
    Fakultat¨ fur¨ Informatik Fachgebiet Vernetzte Rechensysteme Technische Universitat¨ Munchen¨ Flexible Task Management for Self-Adaptation of Mixed-Criticality Systems with an Automotive Example Daniel Andreas Krefft Vollst¨andigerAbdruck der von der Fakult¨atf¨urInformatik der Technischen Universit¨at M¨unchen zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften (Dr.rer.nat.) genehmigten Dissertation. Vorsitzende: Prof. Dr. Claudia Eckert Pr¨ufendeder Dissertation: Prof. Dr. Uwe Baumgarten Prof. Dr.-Ing. Andreas Herkersdorf Die Dissertation wurde am 22.08.2018 bei der Technischen Universit¨atM¨unchen eingereicht und durch die Fakult¨atf¨urInformatik am 11.12.2018 angenommen. Abstract With regard to future connected cars, there are two trends leading to consolidated hard- ware devices as well as an increasing software complexity within a car. In consequence, a rising number of software needs to use the provided resources of a few high-performance hardware devices. For an efficient resource usage, a flexible software management sup- porting the (self-)adaptation of a software system is getting more and more important - even within a car. This flexible software management therefore needs to consider the criticality and real-time properties of an application within this context. Corresponding to the hardware consolidation, the management approach should be combined with the actual application on one hardware device. With a recent advance of multi-core embed- ded systems, there exists a potential hardware platform which is able to support this combination in an embedded context. Especially, the usage of a flexible management supporting the self-adaptation of a mixed-criticality software system on an embedded hardware device during run-time is of interest.
    [Show full text]
  • Microkernel-Based Operating Systems - Introduction
    Faculty of Computer Science Institute for System Architecture, Operating Systems Group Microkernel-based Operating Systems - Introduction Björn Döbel Dresden, Oct 12th 2010 Lecture Goals • Provide deeper understanding of OS mechanisms • Illustrate alternative design concepts • Promote OS research at TU Dresden • Make you all enthusiastic about OS development in general and microkernels in special TU Dresden, 2010-10-12 MOS - Introduction Slide 2 von 41 Administration - Lecture • Lecture every Tuesday, 1:00 PM, INF/E08 • Slides: http://www.tudos.org -> Teaching -> Microkernel-based Operating Systems • Subscribe to our mailing list: http://os.inf.tu-dresden.de/mailman/listinfo/mos2010 • This lecture is not: Microkernel construction (in summer term) TU Dresden, 2010-10-12 MOS - Introduction Slide 3 von 41 Administration - Exercises • Exercises (roughly) bi-weekly, Tuesday, 2:50 PM, INF/E08 • Practical exercises in the computer lab • Paper reading exercises – Read a paper beforehand. – Sum it up and prepare 3 questions. – We expect you to actively participate in discussion. • First exercise: next week – Brinch-Hansen: Nucleus of a multiprogramming system TU Dresden, 2010-10-12 MOS - Introduction Slide 4 von 41 Complex lab • Complex lab in parallel to lecture • Build several components of an OS • “Komplexpraktikum” for (Media) Computer Science students • “Internship” for Computational Engineering • starts on Tuesday, Oct 26th, 14:50 TU Dresden, 2010-10-12 MOS - Introduction Slide 5 von 41 Schedule Date Lecture Exercise Oct 12 Intro Oct 19 Tasks, Threads, Synchronization Paper: Nucleus of an MP system Oct 26 Memory Nov 2 Communication Practical: Booting Nov 9 Real-Time Nov 16 Device Drivers Paper: Singularity OS Nov 23 Nov 30 Resource Management Practical: IPC Dec 7 Virtualization Dec 14 Legacy Containers Paper: Formal req.
    [Show full text]
  • L4 Microkernel
    10 Years L4-Based Systems L4/Nizza Secure-System Architecture TU Dresden Operating Hermann Härtig Systems Group et al. mult. 10 Years Your Passwords, Secrets, ... L4-Based Your Passwords, Secrets, ... Systems applet Linux App Firefox jvm X11 source: Linux Understanding Data Lifetime via Hermann Härtig Whole System Simulation et al. Jim Chow, Ben Pfaff, Tal mult. Garfinkel, Kevin Christopher, TU and Mendel Rosenblum, Dresden Operating keyboard Stanford University Systems Usenix Security 04 Group 2 SEVECOM Budapest 2006 10 Years Outline L4-Based Outline Systems L4 etc . the microkernel vision . early experience: MACH etc . what is L4 ? . L4 and legacy: L4Linux and DDE . DROPS: L4 and Real-Time . L4Env: a multi-server environment for L4 apps Hermann . major L4 projects Härtig et al. mult. TU L4/Nizza Secure System Architecture Dresden Operating What's Up Next? Systems Group Conclusion 3 SEVECOM Budapest 2006 Microkernels - 10 Years Microkernels - L4-Based vision and earlier experience Systems vision and earlier experience . monolithic systems – large – complex – hard to add real-time – large trusted computing bases Applications Applications User Applications – new additional Mode components often crash system Privileged File Network Kernel Hermann Systems Stacks Härtig Mode et al. Memory Processe mult. Manage Drivers s ment TU Dresden Monolithic Operating Operating System Systems Group Hardware 4 SEVECOM Budapest 2006 10 Years The Microkernel Vision L4-Based The Microkernel Vision Systems . small operating system kernel – kernel-mode action less error prone – allows strict validation . system services implemented as user-level servers with their own address spaces – flexibility – extensibility – customizable Hermann . more robust systems Härtig et al. – protected individual system components (e.g., drivers) mult.
    [Show full text]
  • Operating System Structure
    Operating System Structure Joey Echeverria [email protected] modified by: Matthew Brewer [email protected] rampaged through by: Dave Eckhardt [email protected] December 5, 2007 Carnegie Mellon University: 15-410 Fall 2007 Synchronization • P4 - due tonight • Homework 2 - out today, due Friday night • Book report - due Friday night (late days are possible) • Friday lecture - exam review • Exam - room change in progress; discard any cached values Carnegie Mellon University: 15-410 Fall 2007 1 Outline • OS responsibility checklist • Kernel structures – Monolithic kernels ∗ Kernel extensions – Open systems – Microkernels – Provable kernel extensions – Exokernels – More microkernels • Final thoughts Carnegie Mellon University: 15-410 Fall 2007 2 OS Responsibility Checklist • It’s not so easy to be an OS: 1. Protection boundaries 2. Abstraction layers 3. Hardware multiplexers Carnegie Mellon University: 15-410 Fall 2007 3 Protection Boundaries • Protection is “Job 1” – Protect processes from each other – Protect crucial services (like the kernel) from processes • Notes – Implied assumption: everyone trusts the kernel – Kernels are complicated ∗ See Project 3 :) ∗ Something to think about · Full OS is millions of lines of code · Very roughly: correctness ∝ 1/code size Carnegie Mellon University: 15-410 Fall 2007 4 Abstraction Layer • Present “simple”, “uniform” interface to hardware • Applications see a well defined interface (system calls) – Block Device (hard disk, flash card, network mount, USB drive) – CD drive (SCSI, IDE) – tty (teletype,
    [Show full text]
  • DEPARTMENT of LABOR Occupational Safety and Health Administration
    This document is scheduled to be published in the Federal Register on 03/11/2016 and available online at http://federalregister.gov/a/2016-05485, and on FDsys.gov DEPARTMENT OF LABOR Occupational Safety and Health Administration [Docket No. OSHA-2012-0035] Traylor Bros., Inc.; Grant of a Permanent Variance AGENCY: Occupational Safety and Health Administration (OSHA), Labor. ACTION: Notice. SUMMARY: In this notice, OSHA grants a permanent variance to Traylor Bros., Inc., from the provisions of OSHA standards that regulate work in compressed-air environments at 29 CFR 1926.803. DATES: The permanent variance specified by this notice becomes effective on [INSERT DATE OF PUBLICATION IN THE FEDERAL REGISTER] and shall remain in effect until it is modified or revoked. FOR FURTHER INFORMATION CONTACT: Information regarding this notice is available from the following sources: Press inquiries: Contact Mr. Frank Meilinger, Director, OSHA Office of Communications, U.S. Department of Labor, 200 Constitution Avenue, NW., Room N- 3647, Washington, DC 20210; telephone: (202) 693-1999; email: [email protected]. General and technical information: Contact Mr. Kevin Robinson, Director, Office of Technical Programs and Coordination Activities, Directorate of Technical Support and Emergency Management, Occupational Safety and Health Administration, U.S. Department of Labor, 200 Constitution Avenue, NW., Room N-3655, Washington, DC 20210; telephone: (202) 693-2110; email: [email protected]. OSHA’s web page 1 includes information about the Variance Program (see http://www.osha.gov/dts/otpca/variances/index.html). SUPPLEMENTARY INFORMATION: Copies of this Federal Register notice. Electronic copies of this Federal Register notice are available at http://www.regulations.gov.
    [Show full text]