CS 162 Nachos Tutorial and Source Code

Total Page:16

File Type:pdf, Size:1020Kb

CS 162 Nachos Tutorial and Source Code !∀# ! " # $ % & ' ' " ( )$ " # $ % * " ( $ # $ # $ " " " ! % % ,2 " ,2 !33'1 % % +, " . /0 ' ,2 % !-& % " . /0 1 % ) % # $ # 4-$ " # & ! " 4- 55 ) && $ " 4- 6 % 7 " , & & ' & !/4-0 " , & " ) ) ' 4- 8 ' " , & ( ( )$ " ! 9) " ;4- ::55/ &0 " 9 ) 4- ) " 9# '-4 % / 0 2 ' ; % / 0 " < - % )/2 *0 " =4-&>( % / ) -0 % ' '6 ' % /2 0 &' ) % /2 0 4- % -/2 ?0 9 " # ' , " , @ - 6 '',2 ' ' " 2 " A ) / !0 , B " , " C ) " C ) ' - " -E' ) - - " ) ) % , /0 % ! ) 1 ,2 % , /0 % ) 6& % , /0 " )' ) % , )D)/0 ' " - - ' / 0 " ' & " - " (- % /0) ' & -GFF ) / 1 0 % )/0) & / F ) 0 " % )>/0- ) % &/0 % /0 ) % &/0 % (/0 " - 6 7 " 2 - ! (>- " 4- " > ) " % >7) 8 4- 55' % 9/0 &/ 60 7 % 9/0) & " )D) % ( /0 % '& )& - % < 2 * " & ' ) % . && & % -- ) H- ) C " & C " ( ) " " % @/0@ )' B C / & 0 % /0 / &0 " C % /0 / 0 % '='='9 )'3 % /0A - - " ;-C " ; 2 - C & 9 " &4- = " 8- =&/0') " & C ' )/0 " ;1 " I &8 1 " > = = & " ! " 3 " " C @ # $%& $ % C' % && ! $ ! % " > 8 " # C $ " # $ - ( $ " ,2 " 3 6J2 K " " 2 6 " < - " 2 6, " 1 " 2 ?6 +, " . ) " 2 *6 ) > & ;1H;& " /) 0 % 2 8 % 3 " /0 *2 2 " 2 " GLC 8 " 2 , " GL +& / 0 " 2 ? H+, " FL " 2 * ) H> & " FL " ?GL2 " GL= () = & @ " A ! , ) 2 , " & " ?FL3 " 9 ' ' ' ' ' ' ' ' " " GL, % , " 2 E " ?FL ' ( ') ' ( " GLD 2 ? H+, 2 * ) " ?FL D9'-& " MGL ) " *FL2- ' ' % 3 / 0 " GL " ?FLD@ % D)= % > 7 ( " # ) /0 - " A & " >- ) " > ) " 2 8 " = =;>,;') % ; D 1 8 ) 8!C 2 " % ) - 3 , " ! A& ) " =;>,; ' " 3 ' &' " #&2 ' ! 6; & ) ' " = B. 1 &- + &- " ) " = -& ) 6& " # - * ! ) * ! ) * ! ) " ; 2-& * ! ) * * ! ) 09/02/06 19:43:58 nachos/README 1 Nachos for Java README Compiling Nachos: Welcome to Nachos for Java. We believe that working in Java rather than You should now have a directory called nachos, containing a Makefile, C++ will greatly simplify the development process by preventing bugs this README, and a number of subdirectories. arising from memory management errors, and improving debugging support. First, put the ’nachos/bin’ directory on your PATH. This directory Getting Nachos: contains the script ’nachos’, which simply runs the Nachos code. Download nachos-java.tar.gz from the Projects section of the class To compile Nachos, go to the subdirectory for the project you wish homepage at: to compile (I will assume ’proj1/’ for Project 1 in my examples), and run: http://www-inst.EECS.Berkeley.EDU/˜cs162/ gmake Unpack it with these commands: This will compile those portions of Nachos which are relevant to the gunzip -c nachos-java.tar.gz | tar xf - project, and place the compiled .class files in the proj1/nachos directory. Additional software: You can now test Nachos from the proj1/ directory with: Nachos requires the Java Devlopment Kit, version 1.5 or later. This is installed on all instructional machines in: nachos /usr/sww/lang/jdk-1.5.0_05 To use this version of the JDK, be sure that You should see output resembling the following: /usr/sww/lang/jdk-1.5.0_05/bin is on your PATH. (This should be the case for all class accounts nachos 5.0j initializing... config interrupt timer elevators user-check grader already.) *** thread 0 looped 0 times *** thread 1 looped 0 times If you are working at home, you will need to download the JDK. *** thread 0 looped 1 times It is available from: *** thread 1 looped 1 times http://java.sun.com/j2se/1.5/ *** thread 0 looped 2 times Please DO NOT DOWNLOAD the JDK into your class account! Use the *** thread 1 looped 2 times preinstalled version instead. *** thread 0 looped 3 times *** thread 1 looped 3 times The build process for Nachos relies on GNU make. If you are running on *** thread 0 looped 4 times one of the instructional machines, be sure you run ’gmake’, as ’make’ *** thread 1 looped 4 times does not support all the features used. If you are running Linux, the Machine halting! two are equivalent. If you are running Windows, you will need to download and install a port. The most popular is the Cygnus toolkit, Ticks: total 24750, kernel 24750, user 0 available at: Disk I/O: reads 0, writes 0 Console I/O: reads 0, writes 0 http://sources.redhat.com/cygwin/mirrors.html Paging: page faults 0, TLB misses 0 Network I/O: received 0, sent 0 The Cygnus package includes ports of most common GNU utilities to Windows. This is the correct output for the "bare bones" Nachos, without any of the features you will add during the projects. For project 2, you will need a MIPS cross compiler, which is a specially compiled GCC which will run on one architecture (e.g. If you are working on a project which runs user programs (projects 2-4), Sparc) and produce files for the MIPS processor. These compilers you will also need to compile the MIPS test programs with: are already installed on the instructional machines, and are available in the directory specified by the $ARCHDIR environment gmake test variable. Command Line Arguments: If you are working at home, you will need to get a cross-compiler for yourself. Cross-compilers for Linux and Win32 will be available For a summary of the command line arguments, run: from the CS162 Projects web page. Download the cross compiler distribution and unpack it with the following command: nachos -h gunzip -c mips-x86-linux-xgcc.tar.gz | tar xf - The commands are: (Substitute the appropriate file name for mips-x86.linux-xgcc in the -d <debug flags> above command.) You need to add the mips-x86.linux-xgcc directory to Enable some debug flags, e.g. -d ti your PATH, and set an environment variable ARCHDIR to point to this directory. (Again, this has already been done for you on the -h instructional machines.) Print this help message. 09/02/06 19:43:58 nachos/README 2 -s <seed> ElevatorBank.allowElevatorGUI: Specify the seed for the random number generator Normally true. When we grade, this will be false, to prevent malicious students from running a GUI during grading. -x <program> Specify a program that UserKernel.run() should execute, NachosSecurityManager.fullySecure: instead of the value of the configuration variable Normally false. When we grade, this will be true, to enable Kernel.shellProgram additional security checks. -z Kernel.kernel: print the copyright message Specifies what kernel class to dynmically load. For proj1, this is nachos.threads.ThreadedKernel. For proj2, this should be -- <grader class> nachos.userprog.UserKernel. For proj3, nachos.vm.VMKernel. For Specify an autograder class to use, instead of proj4, nachos.network.NetKernel. nachos.ag.AutoGrader Processor.usingTLB: -# <grader arguments> Specifies whether the MIPS processor provides a page table Specify the argument string to pass to the autograder. interface or a TLB interface. In page table mode (proj2), the processor accesses an arbitrarily large kernel data structure to do -[] <config file> address translation. In TLB mode (proj3 and proj4), the processor Specifiy a config file to use, instead of nachos.conf maintains a small TLB (4 entries). Processor.numPhysPages: Nachos offers the following debug flags: The number of pages of physical memory. Each page is 1K. This is normally 64, but we can lower it in proj3 to see whether projects c: COFF loader info thrash or crash. i: HW interrupt controller info p: processor info Documentation: m: disassembly M: more disassembly The JDK provides a command to create a set of HTML pages showing all t: thread info classes and methods in program. We will make these pages available on a: process info (formerly "address space", hence a) the webpage, but you can create your own for your home machine by doing the following (from the nachos/ directory): To use multiple debug flags, clump them all together. For example, to monitor coff info and process info, run: mkdir ../doc gmake doc nachos -d ac Troubleshooting: nachos.conf: If you receive an error about "class not found exception", it may be When Nachos starts, it reads in nachos.conf from the current because you have not set the CLASSPATH environment variable. Add the directory. It contains a bunch of keys and values, in the simple following to your .cshrc: format "key = value" with one key/value pair per line. To change the default scheduler, default shell program, to change the amount of setenv CLASSPATH . memory the simulator provides, or to reduce network reliability, modify this file. Credits: Machine.stubFileSystem: Nachos was originally written by Wayne A. Christopher, Steven J. Specifies whether the machine should provide a stub file system. A Procter, and Thomas E. Anderson. It incorporates the SPIM simulator stub file system just provides direct access to the test directory. written by John Ousterhout. Nachos was rewritten in Java by Daniel Since we’re not doing the file system project, this should always Hettena. be true. Copyright: Machine.processor: Specifies whether the machine
Recommended publications
  • Überconf Westin Westminster June 19 - 22, 2012
    ÜberConf Westin Westminster June 19 - 22, 2012 Tue, Jun. 19, 2012 Westminster I Westminster II Standley I Standley II Lake House Cotton Creek Meadowbrook I Meadowbrook II Windsor 8:00 - 9:00 AM EARLY REGISTRATION: PRE-CONFERENCE WORKSHOP ATTENDEES ONLY - WESTMINSTER BALLROOM FOYER 9:00 - 6:00 PM Programming iOS Workshop Android Web Application Domain-Driven Git Bootcamp with HTML 5 Christopher Judd Workshop Security Design (DDD) - An All-Day Venkat James Harmon Workshop Workshop Workshop Subramaniam Ken Sipe Paul Rayner Matthew McCullough 5:00 - 6:30 PM MAIN UBERCONF REGISTRATION - WESTMINSTER BALLROOM FOYER 6:30 - 8:30 PM DINNER/KEYNOTE - WESTMINSTER BALLROOM 3/4 7:30 - 8:30 PM Keynote: by Tim Berglund 8:30 - 10:30 PM OPENING NIGHT OUTDOOR RECEPTION - SOUTH COURTYARD ÜberConf Westin Westminster June 19 - 22, 2012 Wed, Jun. 20, 2012 Westminster I Westminster II Standley I Standley II Lake House Cotton Creek Meadowbrook I Meadowbrook II Windsor 7:00 - 8:00 AM 5K FUN RUN & POWER WALK - MEET IN LOBBY 7:30 - 8:30 AM BREAKFAST & LATE REGISTRATION - WESTMINSTER BALLROOM 3/4 8:30 - 10:00 AM Succeeding Scala for Professional Effective Spring NoSQL Build Lifecycle Developer guide OOP Principles The Who and with the Apache the Intrigued Javascript Workshop Smackdown 2012 Craftsmanship to the cloud Ken Sipe What of Agile - SOA stack Venkat development Craig Walls Tim Berglund Tools Pratik Patel Personas and Johan Edstrom Subramaniam for the Java Matthew Story Maps developer McCullough Nathaniel Schutta Peter Bell 10:00 - 10:30 AM MORNING BREAK 10:30
    [Show full text]
  • Resource-Oriented Computing W/ Netkernel
    Resource-Oriented Computing w/ NetKernel : Software for the 21st Century Brian Sletten Zepheira, LLC [email protected] Speaker Qualifications Over 14 years of software development experience Has own software consulting company for design, mentoring, training and development Currently working in Semantic Web, AOP, Grid Computing, P2P and security consulting Pinky Committer Agenda What the heck is NetKernel? Why We Care NetKernel Overview NetKernel Languages Advanced Concepts Pinky What the heck is NetKernel? A micro-kernel based resource ecosystem built around the principles of REST, Unix Pipes and SOA Why We Care: The Simple Answer Most enterprise systems use XML and are built in Java and this is still too much of a pain Complicated Different Languages for different technologies Predicting scalability Why We Care : The Complicated Answer This is hard because of a general mismatch at the intersection of languages, data model, processing abstractions, architectural tiers, etc. Larger Trends Data formatted Code written 1970s 1980s 1990s 2000s NetKernel A Ground-Up Resource-oriented computing environment Modern, microkernel architecture Takes the best of REST, Unix Pipes, SOA Open Source w/ Dual License for non-open source uses Resource-Oriented Computing Everything is a Resource Everything is URI-Addressable (logical reference) “Computation” is the turning of logical resource references into physical representation Lossless conversion between representations REST Representational State Transfer Architectural style described in Roy Fielding’s
    [Show full text]
  • Resource-Oriented Architecture Patterns for Webs of Data Synthesis Lectures on the Semantic Web: Theory and Technology
    SLETTEN OFDATA WEBS FOR RESOURCE-ORIENTED PATTERNS ARCHITECTURE Series ISSN: 2160-4711 SYNTHESIS LECTURES ON M Morgan & Claypool Publishers THE SEMANTIC WEB: THEORY AND TECHNOLOGY &C Series Editors: James Hendler, Rensselaer Polytechnic Institute Ying Ding, Indiana University Resource-Oriented Resource-Oriented Architecte Patterns for Webs of Data Brian Sletten, Bosatsu Consulting Architecture Patterns for The surge of interest in the REpresentational StateTransfer (REST) architectural style, the Semantic Web, and Linked Data has resulted in the development of innovative, flexible, and powerful systems that embrace one or more of these compatible technologies. However, most developers, Webs of Data architects, Information Technology managers, and platform owners have only been exposed to the basics of resource-oriented architectures. This book is an attempt to catalog and elucidate several reusable solutions that have been seen in the wild in the now increasingly familiar “patterns book” style. These are not turnkey implementations, but rather, useful strategies for solving certain problems in the development of modern, resource-oriented systems, both on the public Web and within an organization’s firewalls. Brian Sletten About SYNTHESIs This volume is a printed version of a work that appears in the Synthesis Digital Library of Engineering and Computer Science. Synthesis Lectures MORGAN provide concise, original presentations of important research and development topics, published quickly, in digital and print formats. For more information
    [Show full text]
  • Quick Reference to Netkernel V4 Resource Oriented Platform
    Contents Include: Resource Oriented Primer Quick Reference to Standard Modules Identifier Grammars NetKernel v4 Resource Oriented Platform NetKernel Foundation API About NetKernel request. NetKernel is a Resource Oriented Computing Platform developed Accessor ± the most common type of endpoint provides access to by 1060 Research. It is based upon the Java Standard Edition a resources state. Also typically embodies transformation platform but incorporates many standards and implementations functions and language runtimes. from elsewhere. It is distributed in two flavours, Standard Edition Transreptor ± a specialised endpoint which will convert which is licensed under an open source 1060 Public License and an information in one representation to the same information Enterprise Edition which is commercially licensed. Uses of in another representational form. Usually used to adapt NetKernel range from application server, rich client, (or representations between an endpoint and it©s client. combinations of both), with HTTP transports and many others through to very small footprint standalone applications and Transport ± a specialised endpoint which receives events from embedded with Java containers. outside the resource oriented system and adapts them to a request. Transports may return responses too. What makes NetKernel different Overlay ± a specialised endpoint which wraps a space and issues NetKernel is based upon the Resource Oriented Computing (ROC) sub-requests into it. This provides the basis for patterns concept rather than the Object Oriented Programming (OOP) such as importing spaces into other spaces. concept used by much of today©s software. Research initiated at Request Scope ± an ordered list of spaces within a request which Hewlett Packard Labs showed how this unique approach which are used to determine resolution.
    [Show full text]
  • Document Schema Definition Languages (DSDL)
    ISO/IEC PDTR 19757-10 Contents Page Foreword................................................................................................................................................................... iv Introduction............................................................................................................................................................... v 1 Scope............................................................................................................................................................ 1 2 Normative references.................................................................................................................................. 1 3 Terms and definitions.................................................................................................................................. 1 4 Using Pipelining for Validation Management............................................................................................ 2 4.1 Validation Management using DPML......................................................................................................... 2 4.1.1 Example of Linear DPML............................................................................................................................. 3 4.1.2 Example of Asynchronous DPML............................................................................................................... 7 4.2 Validation Management using Cocoon...................................................................................................
    [Show full text]
  • Space Details
    Space Details Key: GROOVY Name: Groovy Description: Documentation and web site of the Groovy scripting language for the JVM. Creator (Creation Date): bob (Apr 15, 2004) Last Modifier (Mod. Date): glaforge (Apr 12, 2005) Available Pages • Home • Advanced Usage Guide • Ant Task Troubleshooting • BuilderSupport • Compiling Groovy • Compiling With Maven2 • Design Patterns with Groovy • Abstract Factory Pattern • Adapter Pattern • Bouncer Pattern • Chain of Responsibility Pattern • Composite Pattern • Decorator Pattern • Delegation Pattern • Flyweight Pattern • Iterator Pattern • Loan my Resource Pattern • Null Object Pattern • Pimp my Library Pattern • Proxy Pattern • Singleton Pattern • State Pattern • Strategy Pattern • Template Method Pattern • Visitor Pattern • Dynamic language beans in Spring • Embedding Groovy • Influencing class loading at runtime • Make a builder • Mixed Java and Groovy Applications • Optimising Groovy bytecodes with Soot Document generated by Confluence on Dec 07, 2007 12:38 Page 1 • Refactoring with Groovy • Introduce Assertion • Replace Inheritance with Delegation • Security • Writing Domain-Specific Languages • Articles • Community and Support • Contributing • Mailing Lists • Related Projects • User Groups • Cookbook Examples • Accessing SQLServer using groovy • Alternate Spring-Groovy-Integration • Batch Image Manipulation • command line groovy doc or methods lookup • Compute distance from Google Earth Path (in .kml file) • Convert SQL Result To XML • Embedded Derby DB examples • Embedding a Groovy Console in
    [Show full text]
  • Pragpub #066, December 2014
    The Pragmatic Bookshelf PragPThe Secondu Iterationb IN THIS ISSUE * Rothman and Lester on mentoring * Marcus Blankenship on managing programmers * Ron Hitchens on Resource Oriented Computing vs Object Oriented Computing * Brian Sletten on Resource Oriented Computing vs Microservices * Tom Geudens on Resource Oriented Computing * Dan Wohlbruck on the C language * Antonio Cangiano on new books for programmers Issue #66 December 2014 PragPub • December 2014 Contents FEATURES Your Object Model Sucks ................................................................................... 15 by Ron Hitchens The big idea in Object Oriented Programming was always messaging, not objects or classes. Resource Oriented Programming gets that right. Microservices Is not the Answer ..................................................................... 23 by Brian Sletten Microservices has the right idea. It just doesn’t take it far enough. Introducing Resource Oriented Computing ................................................. 33 by Tom Geudens There’s a program that’s been running for 25 years, that scales like nobody’s business, and that’s based on open protocols. Can your code measure up to that? The Evolution of C ............................................................................................... 44 by Dan Wohlbruck Dan continues his series on the history of programming languages with more on C. — i — DEPARTMENTS On Tap .......................................................................................................................
    [Show full text]
  • Resource-Oriented Computing® and Netkernel® 5
    1060 Research Limited - NetKernel and Resource-Oriented Computing 1060 Research Limited Collection of Articles Resource-Oriented Computing® and NetKernel® 5 v 1.1.1 1060 Research Limited - NetKernel and Resource-Oriented Computing 1060, NetKernel, Resource Oriented Computing, ROC are respectively registered trademark and trademarks of 1060 Research Limited 2001-2013 © 1060 Research Limited 1060 Research Limited - NetKernel and Resource-Oriented Computing Simplicity is the ultimate sophistication. Leonardo da Vinci ost software today is very much like an M Egyptian pyramid with millions of bricks piled on top of each other, with no struc- tural integrity, but just done by brute force and thousands of slaves. Dr. Alan Kay (father of OO programming) his software transformation, whatever it is, is coming. It must come; because we sim- T ply cannot keep piling complexity upon complexity. We need some new organizing principle that revamps the very foundations of the way we think about software and opens up vistas that will take us into the 22nd century. Robert Cecil Martin, aka “Uncle Bob” n order to handle large systems over time, there needs to be a high level description of I information...a language which allows the uniform representation of information. Algo- rithms is one type of information that has to do with computations, but there are other types. ...Computations need not be arranged in programs; they must be information, standing on their own, allowing the user to mix them at will, just like with any other type of informa- tion.
    [Show full text]
  • Operating System
    Operating System Operating System Concepts and Techniques M. Naghibzadeh Professor of Computer Engineering iUniverse, Inc. New York Lincoln Shanghai Operating System Concepts and Techniques Copyright © 2005 by Mahmoud Naghibzadeh All rights reserved. No part of this book may be used or reproduced by any means, graphic, electronic, or mechanical, including photocopying, recording, taping or by any information storage retrieval system without the written permission of the publisher except in the case of brief quotations embodied in critical articles and reviews. iUniverse books may be ordered through booksellers or by contacting: iUniverse 2021 Pine Lake Road, Suite 100 Lincoln, NE 68512 www.iuniverse.com 1-800-Authors (1-800-288-4677) ISBN-13: 978-0-595-37597-4 (pbk) ISBN-13: 978-0-595-81992-8 (ebk) ISBN-10: 0-595-37597-9 (pbk) ISBN-10: 0-595-81992-3 (ebk) Printed in the United States of America Contents Preface ..................................................................................................xiii Chapter 1 Computer Hardware Organization ..................................1 1.1 The Fetch-Execute Cycle ......................................................................2 1.2 Computer Hardware Organization ....................................................4 1.3 Summary ..............................................................................................7 1.4 Problems ..............................................................................................7 Recommended References ........................................................................8
    [Show full text]
  • Technical Paper, ROCAS V1.2 Cg 1060 Research Ltd 1
    Technical Paper, ROCAS v1.2 c 1060 Research Ltd Abstract Today's software systems have a much shorter life span than other engineering arti- facts. Code is brittle and system architectures are rigid and not robust to change. With the Web an alternative model of computing has taken shape, a model that allows for change on a small scale inside of a complex and large-scale system. The core abstrac- tion behind the Web can be applied to the design of software systems. The abstraction in Resource Oriented Computing generalizes the Web abstraction to enable the most adaptable software systems and architectures that evolve with change. 1 Resource Oriented Computing for Adaptive Systems Peter J. Rodgers, PhD, [email protected] May 2015 1 Challenge The second Law of Thermodynamics states that entropy will always increase. The challenge faced by long-lived resource adaptive systems is to fight entropy with the least possible expenditure of energy (physical, computational, financial). 2 Definitions "Myriad computational systems, both hardware and It is helpful to start by stating some definitions so that we may clarify concepts such as software, are organized as \stability" and \evolvability" as applied to adaptive computation systems. state-transition systems. Such a system evolves over It will be shown that we can obtain a useful working understanding of stability and time (or, computes) by evolvability by considering computational state.1 continually changing state We require to maintain a conceptual distinction between a given logical abstract potential in response to one or more discrete stimuli (typically state and an instantaneous physical representation of the state.
    [Show full text]