CS 0449 - Introduction to Systems Software

Fall 2020

Contact Information

Course Description and Goals

A Computer System is comprised of both hardware and software working in concert to accomplish useful work. In this course, we will explore the issues of programming a real computer system by examining the abstractions, interfaces, and design decisions that influence the way that software runs. This includes the role the Operating System has in communication and resource management.

The perspective we will take is one of the lifecycle of a program from implementation to execution. The simple act of compiling and running a program, a sequence of events we often take for granted, is a complex interaction of many different components that work together to manage the computer’s resources and perform the desired task. Together, these components form a working computer system.

This course begins with the creation of executable programs in the C programming language. We will then explore the resultant program as it is stored on disk and as it is loaded for execution. Next, we will examine the interactions between our code and the code provided via libraries or the operating system to facilitate common, low-level tasks. Finally, we will look at the abstractions and resource management undertaken by the OS and its drivers to facilitate communication and hardware interaction.

The goals of the course are:

1.     Learning C programming. C is the most common language used for systems software.

2.     Exploring the layout of an executable programs code and data both as stored on disk and loaded into memory.

3.     Interacting with the abstractions that libraries and the operating system provide.

4.     Implementing our own abstractions and managing hardware resources through device drivers.

Prerequisites

Before enrolling in this course, you need to have completed CS/COE 0445 Data Structures and have completed or be currently enrolled in CS/COE 0447 Computer Organization and Assembly Language Programming. If you have any questions about the prerequisite material for the course, please ask at the beginning of the term.

Textbooks

We will be using one primary textbook extensively. You should acquire a copy if possible:

CS:APP3e: Randal E. Bryant and David R. O'Hallaron, Computer Systems: A Programmer's Perspective, Third Edition, Pearson, 2016

Electronic version is available for $34.99. See: https://www.vitalsource.com/products/computer-systems-a-programmer-39-s-perspective-randal-e-bryant-david-r-v9780134092997.

A good reference on the C programming language is recommended. There are many online resources of various quality. One classic book is:

1.     K&R 2e: Brian W. Kernighan and Dennis M. Ritchie, The C Programming Language, Second Edition, Prentice Hall, 1988 . ISBN: 0-13110-362-8.

2.     Oualline: Steve. Practical C Programming. OReilly, Sebastopol, CA, 1997. ISBN: 1-56592-306-5

There are additional textbooks that are available online in PDF form and are highly relevant to the course topics.

Misurda: Jonathan Misurda, CS 0449: Introduction to Systems Software (online).

ALP: Mark Mitchell, Jeffrey Oldham, and Alex Samuel, Advanced Linux Programming (online).

LDD3: Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman, Linux Device Drivers, Third Edition (online).

Grading Policy

Labs (50%): There are eight programming lab assignments that are the fundamental piece of this course and will be conducted during recitations. Lab assignments will be posted on Canvas and turned in electronically on Gradescope and will be graded mostly automatically. It is worth noting that much of what you learn in this course will be through completing these assignments. Late submissions are allowed for up to two days with a 10% reduction per late day.

Midterm and Final exams (20%): There will be one midterm exam and a final exam. There will be questions to test your understanding of the topics covered in lecture material and lab assignments. No collaboration of any form is allowed on exams. Students must not discuss any aspect of any exam question with someone who has not yet taken the exam. Make-up exams can be scheduled well in advance. The exams are remote and non-cumulative.

Homework assignments (20%)

Lecture Participation (10%): Mini-quizzes on Top Hat during each lecture. The join code for Top Hat is 389666.

Regrade requests should be submitted within a week of when the grade item was graded.

Important Dates

(Tentative)

Weekly Schedule

(Tentative)

Communication Policy

There are many ways to communicate with the teaching team. Please reach out to us as early as possible and as frequently as possible. You can reach us on:

·       Piazza

·       Canvas Messages

·       Email

Please expect a response within 72 hours.

COVID-19 Statement

I would like to emphasize that my number one concern is your safety and health, both physical and mental.  My goal is for each and every one of you to succeed in the course. I am here to support you and I will remain understanding and flexible given the challenges that we are all facing together. The lectures and recitations will be recorded, and the recorded sessions include your participation. The recorded sessions will be made available through Canvas and only to this term's class. Although I expect you to attend the live lectures and recitations, attendance is not taken. The Tophat questions that are offered during the live lectures will also be assigned as homework. 

Minimum Technology Requirements

Basic computer hardware that includes camera and microphone for the Zoom meetings. Basic software (e.g., Microsoft Suite, Canvas, Panopto, Top Hat, Zoom, Gradescope, Piazza, PuTTY, WinSCP or FileZilla, a text editor (e.g., Atom, Sublime, VS Code, Notepad++, Brackets, etc.).

Students with Disabilities

If you have a disability for which you are or may be requesting an accommodation, you are encouraged to contact both your instructor and Disability Resources and Services (DRS), 140 William Pitt Union, (412) 648-7890, drsrecep@pitt.edu, (412) 228-5347 for P3 ASL users, as early as possible in the term. DRS will verify your disability and determine reasonable accommodations for this course.

Academic Integrity

All assignment submissions must be the sole work of each individual student. Students may not read or copy another student's solutions or share their own solutions with other students. Students may not review solutions from students who have taken the course in previous years. Submissions that are substantively similar will be considered cheating by all students involved, and as such, students must be mindful not to post their code publicly. The use of books and online resources is allowed, but must be credited in submissions, and material may not be copied verbatim. Any use of electronics or other resources during an examination will be considered cheating. If you have any doubts about whether a particular action may be construed as cheating, ask the instructor for clarification before you do it. The instructor will make the final determination of what is considered cheating. Cheating in this course will result in a grade of F for the course and may be subject to further disciplinary action. Should a student be accused of a breach of academic integrity or have questions regarding faculty responsibilities, procedural safeguards including provisions of due process have been designed to protect student rights. These may be found in Guidelines on Academic Integrity: Academic Integrity Policy of the School of Computing and Information.

Pay attention to the following examples of cheating, which include:

§      Sharing code: either by copying, retyping, looking at, or supplying a copy of a file from this or a previous semester.

§      Describing code: Verbal description of code from one person to another.

§      Coaching: Helping your friend to write a lab, line by line.

§      Copying: Copying code from the Web or another student. You are only allowed to use code that we provide you.

§      Searching: Searching the Web for solutions or for any advice on the lab.

Cheating is also looking at other students’ code or allowing others to look at yours. This includes one person looking at code and describing it to another. Be sure to store your work in protected directories (e.g., under the private folder on your AFS space on the department servers), and log off when you leave a remote server, to prevent others from copying your work without your explicit assistance.

You may find it useful to know what is not cheating:

§      Clarifying ambiguities or vague points in class handouts, lectures, or textbooks.

§      Helping others use the computer systems, networks, compilers, debuggers, profilers, or other system facilities.

§      Helping others with high-level design issues only, but algorithm/coding and other such details are not ``high-level design issues''.

§      Helping others with high-level (not code-based) debugging.

§      Using code from the skeleton/package provided in class is always OK.

For a first offense, a student caught collaborating or cheating in any way will receive a zero for the exam, homework, lab, or project in question. In the event of a second offense, the student will receive an F for the course and may be subject to stronger action. They will be reported to the school following University procedures. Submissions that are alike in a substantive way (not due to coincidence) will be considered to be cheating by ALL involved parties. Please protect yourselves by only storing your files in private directories, and by retrieving all printouts promptly.

Religious Observances

In order to accommodate the observance of religious holidays, students should inform the instructor (by email, within the first two weeks of the term) of any such days which conflict with scheduled class activities.

Diversity and Inclusion Statement

I consider this classroom to be a place where you will be treated with respect, and I welcome individuals of all ages, backgrounds, beliefs, ethnicities, genders, gender identities, gender expressions, national origins, religious affiliations, sexual orientations, ability – and other visible and nonvisible differences. All members of this class are expected to contribute to a respectful, welcoming and inclusive environment for every other member of the class. (American Society for Engineering Education)

Copyright Statement

These materials may be protected by copyright. United States copyright law, 17 USC section 101, et seq., in addition to University policy and procedures, prohibit unauthorized duplication or retransmission of course materials. See Library of Congress Copyright Office and the University Copyright Policy.

Classroom Recording

To ensure the free and open discussion of ideas, students may not record classroom lectures, discussion and/or activities without the advance written permission of the instructor, and any such recording properly approved in advance can be used solely for the student’s own private use.

Acknowledgements

The material of this course are based on Dr. Petrucci's CS 0449 course.