Skip to content

Latest commit

 

History

History
133 lines (85 loc) · 3.48 KB

README.md

File metadata and controls

133 lines (85 loc) · 3.48 KB

Pintos

Resources

Requirements

sudo apt install build-essential qemu-system-x86

Project notes

We leave some technical notes we wrote about the assignments that you can find useful.

They are located in the notes/ directory.

System setup

There's an env file we wrote file that provides you several utilities that you can call directly from your terminal:

source env

For docker users:

docker compose up --build

In another terminal, run:

docker compose exec pintos bash
root@pwn13:~# cd pintos/src/threads/
root@pwn13::~/pintos/src/threads# make
root@pwn13::~/pintos/src/threads# cd build
root@pwn13::~/pintos/src/threads/build# pintos --qemu --

Pintos has succesfully booted! :)

Run multiple alarm:

root@pwn13::~/pintos/src/threads/build# pintos --qemu -- run alarm-multiple

️🔎 Debugging

Beyond writing printf all over the place, it's highly recommended to open a GDB session for debugging.

The better way to debug a test is to directly set a breakpoint in the test function:

(gdb) debugpintos
(gdb) b test_alarm_multiple
(gdb) c

Common debugging commands

dumplist &all_list thread allelem
dumplist &all_list thread allelem
dumplist &sleep_list thread allelem

File structure

Pintos entry point is located in src/threads/init.c#main.

  • threads/

    Source code for the base kernel, which you will modify starting in project 1.

  • userprog/

    Source code for the user program loader, which you will modify starting with project 2.

  • vm/

    An almost empty directory. You will implement virtual memory here in project 3.

  • filesys/

    Source code for a basic file system. You will use this file system starting with project 2, but you will not modify it until project 4.

  • devices/

    Source code for I/O device interfacing: keyboard, timer, disk, etc. You will modify the timer implementation in project 1. Otherwise you should have no need to change this code.

  • lib/

    An implementation of a subset of the standard C library. The code in this directory is compiled into both the Pintos kernel and, starting from project 2, user programs that run under it. In both kernel code and user programs, headers in this directory can be included using the #include <...> notation. You should have little need to modify this code.

  • lib/kernel/

    Parts of the C library that are included only in the Pintos kernel. This also includes implementations of some data types that you are free to use in your kernel code: bitmaps, doubly linked lists, and hash tables. In the kernel, headers in this directory can be included using the #include <...> notation.

  • lib/user/

    Parts of the C library that are included only in Pintos user programs. In user programs, headers in this directory can be included using the #include <...> notation.

  • tests/

    Tests for each project. You can modify this code if it helps you test your submission, but we will replace it with the originals before we run the tests.

  • examples/

    Example user programs for use starting with project 2.

  • misc/, utils/

    These files may come in handy if you decide to try working with Pintos on your own machine. Otherwise, you can ignore them.