Pintos

Implements the PintOS OS with priority scheduling, system calls, virtual memory, and a growable file system using indexed and sparse allocation.

hoonably/pintos hoonably/pintos

PintOS Project

UNIST CSE 311 Operating System

20201118 Jeonghoon Park
20201032 Deokhyeon Kim


Setup

Building the Docker Image

📁 Make sure you are inside the setting/ directory before building the image:

cd setting

For amd64 (x86_64) – Windows

sudo docker build -t pintos-image .

For ARM64 (Apple Silicon – macOS)

docker build --platform=linux/amd64 -t pintos-image .
⚠️ Rosetta must be enabled for x86_64 emulation on Apple Silicon. ![Rosetta Setting](https://github.com/user-attachments/assets/b73e6e6e-b851-4611-82ce-3899333feb6e)


Running the Container

📁 Before running the container, move to the project root directory (so that the pintos/ folder is mounted correctly):

cd ..

On amd64 (x86_64) – Windows

sudo docker run -it -p 80:80 \
  -v $(pwd)/pintos:/root/pintos \
  --name pintos pintos-image

On ARM64 (Apple Silicon – macOS)

docker run --platform=linux/amd64 -it -p 80:80 \
  -v $(pwd)/pintos:/root/pintos \
  --name pintos pintos-image


⚠️ First-Time Setup (Install Bochs in the Container)

After the first run, enter the container and run:

cd /root/pintos/src/misc
env SRCDIR=/root/ PINTOSDIR=/root/pintos/ DSTDIR=/usr/local ./bochs-2.2.6-build.sh
cd ..

You only need to do this once, unless the container is deleted.

Once inside the container, you can exit by typing exit or pressing Ctrl+D. This will automatically stop the container as long as no background processes are keeping it alive.

🔁 Subsequent Runs

To start the container again after it has been created:

docker start -ai pintos





🧪 Project Test Results

Each project is implemented and tested on a separate branch. To view and re-run the tests for each project, follow the instructions below.

📂 Project 1 – Threads (Partial Implementation)

Manual: Pintos Project 1

This project involved modifying the thread scheduler and timer mechanisms in PintOS. We implemented the alarm clock and priority-based scheduling, but priority donation was not included as it was optional.

📌 Related Code

  • threads/thread.c, threads/thread.h – Alarm list logic, priority-aware scheduling (thread_set_priority(), thread_get_priority())
  • devices/timer.c – Reimplemented timer_sleep() using sleep queue
  • lib/kernel/list.c – Priority comparison for thread queue ordering

🔧 Check

git checkout project1
docker start -ai pintos

cd /root/pintos/src/threads
make clean
make check
📋 Result

9 / 9 tests passed

pass tests/threads/alarm-single
pass tests/threads/alarm-multiple
pass tests/threads/alarm-simultaneous
pass tests/threads/alarm-priority
pass tests/threads/alarm-zero
pass tests/threads/alarm-negative
pass tests/threads/priority-change
pass tests/threads/priority-fifo
pass tests/threads/priority-preempt

📂 Project 2 – User Programs (Full Implementation)

Manual: Pintos Project 2

This project consisted of two parts:

  • 2-1: Argument passing, system call framework, and basic file I/O
  • 2-2: Full implementation of user-level system calls

The final submission includes both phases, with complete support for all required functionality and test cases.

📌 Related Code

  • userprog/process.c – Executable loading, argument stack setup, and child process tracking
  • userprog/syscall.c – System call interface: read, write, exec, wait, remove, filesize, seek, tell, etc.
  • lib/user/syscall.c – User-space syscall interface
  • lib/string.c, threads/thread.c – String helpers, per-thread file descriptor table
  • filesys/file.c, filesys/inode.c – Backend logic used by syscall layer for file operations

🔧 Check

git checkout project2-2
docker start -ai pintos

cd /root/pintos/src/userprog
make clean
make check
📋 Result

76 / 76 tests passed

pass tests/filesys/base/syn-write
pass tests/userprog/args-none
pass tests/userprog/args-single
pass tests/userprog/args-multiple
pass tests/userprog/args-many
pass tests/userprog/args-dbl-space
pass tests/userprog/sc-bad-sp
pass tests/userprog/sc-bad-arg
pass tests/userprog/sc-boundary
pass tests/userprog/sc-boundary-2
pass tests/userprog/halt
pass tests/userprog/exit
pass tests/userprog/create-normal
pass tests/userprog/create-empty
pass tests/userprog/create-null
pass tests/userprog/create-bad-ptr
pass tests/userprog/create-long
pass tests/userprog/create-exists
pass tests/userprog/create-bound
pass tests/userprog/open-normal
pass tests/userprog/open-missing
pass tests/userprog/open-boundary
pass tests/userprog/open-empty
pass tests/userprog/open-null
pass tests/userprog/open-bad-ptr
pass tests/userprog/open-twice
pass tests/userprog/close-normal
pass tests/userprog/close-twice
pass tests/userprog/close-stdin
pass tests/userprog/close-stdout
pass tests/userprog/close-bad-fd
pass tests/userprog/read-normal
pass tests/userprog/read-bad-ptr
pass tests/userprog/read-boundary
pass tests/userprog/read-zero
pass tests/userprog/read-stdout
pass tests/userprog/read-bad-fd
pass tests/userprog/write-normal
pass tests/userprog/write-bad-ptr
pass tests/userprog/write-boundary
pass tests/userprog/write-zero
pass tests/userprog/write-stdin
pass tests/userprog/write-bad-fd
pass tests/userprog/exec-once
pass tests/userprog/exec-arg
pass tests/userprog/exec-multiple
pass tests/userprog/exec-missing
pass tests/userprog/exec-bad-ptr
pass tests/userprog/wait-simple
pass tests/userprog/wait-twice
pass tests/userprog/wait-killed
pass tests/userprog/wait-bad-pid
pass tests/userprog/multi-recurse
pass tests/userprog/multi-child-fd
pass tests/userprog/rox-simple
pass tests/userprog/rox-child
pass tests/userprog/rox-multichild
pass tests/userprog/bad-read
pass tests/userprog/bad-write
pass tests/userprog/bad-read2
pass tests/userprog/bad-write2
pass tests/userprog/bad-jump
pass tests/userprog/bad-jump2
pass tests/userprog/no-vm/multi-oom
pass tests/filesys/base/lg-create
pass tests/filesys/base/lg-full
pass tests/filesys/base/lg-random
pass tests/filesys/base/lg-seq-block
pass tests/filesys/base/lg-seq-random
pass tests/filesys/base/sm-create
pass tests/filesys/base/sm-full
pass tests/filesys/base/sm-random
pass tests/filesys/base/sm-seq-block
pass tests/filesys/base/sm-seq-random
pass tests/filesys/base/syn-read
pass tests/filesys/base/syn-remove
pass tests/filesys/base/syn-write
All 76 tests passed.

📂 Project 3 – Virtual Memory (Partial Implementation)

Manual: Pintos Project 3

This project required implementing virtual memory features such as supplemental page tables, demand paging, stack growth, and swapping. Due to time constraints, only a subset of core VM functionality was implemented, focusing on demand paging and stack growth.

📌 Related Code

  • vm/frame.c, vm/frame.h – Frame table and eviction policy
  • vm/page.c, vm/page.h – Supplemental page table, lazy loading, and memory tracking
  • vm/swap.c, vm/swap.h – Swap disk interface and slot management
  • userprog/exception.c – Page fault handler
  • userprog/process.c – Stack growth and lazy segment loading

📌 All code in the vm/ directory was written from scratch, as the directory is empty by default.

🔧 Check

git checkout project3
docker start -ai pintos

cd /root/pintos/src/vm
make clean
make check
📋 Result

108 / 109 tests passed FAIL tests/vm/page-parallel ← only failure due to parallel page access

pass tests/filesys/base/syn-write
pass tests/userprog/args-none
pass tests/userprog/args-single
pass tests/userprog/args-multiple
pass tests/userprog/args-many
pass tests/userprog/args-dbl-space
pass tests/userprog/sc-bad-sp
pass tests/userprog/sc-bad-arg
pass tests/userprog/sc-boundary
pass tests/userprog/sc-boundary-2
pass tests/userprog/halt
pass tests/userprog/exit
pass tests/userprog/create-normal
pass tests/userprog/create-empty
pass tests/userprog/create-null
pass tests/userprog/create-bad-ptr
pass tests/userprog/create-long
pass tests/userprog/create-exists
pass tests/userprog/create-bound
pass tests/userprog/open-normal
pass tests/userprog/open-missing
pass tests/userprog/open-boundary
pass tests/userprog/open-empty
pass tests/userprog/open-null
pass tests/userprog/open-bad-ptr
pass tests/userprog/open-twice
pass tests/userprog/close-normal
pass tests/userprog/close-twice
pass tests/userprog/close-stdin
pass tests/userprog/close-stdout
pass tests/userprog/close-bad-fd
pass tests/userprog/read-normal
pass tests/userprog/read-bad-ptr
pass tests/userprog/read-boundary
pass tests/userprog/read-zero
pass tests/userprog/read-stdout
pass tests/userprog/read-bad-fd
pass tests/userprog/write-normal
pass tests/userprog/write-bad-ptr
pass tests/userprog/write-boundary
pass tests/userprog/write-zero
pass tests/userprog/write-stdin
pass tests/userprog/write-bad-fd
pass tests/userprog/exec-once
pass tests/userprog/exec-arg
pass tests/userprog/exec-multiple
pass tests/userprog/exec-missing
pass tests/userprog/exec-bad-ptr
pass tests/userprog/wait-simple
pass tests/userprog/wait-twice
pass tests/userprog/wait-killed
pass tests/userprog/wait-bad-pid
pass tests/userprog/multi-recurse
pass tests/userprog/multi-child-fd
pass tests/userprog/rox-simple
pass tests/userprog/rox-child
pass tests/userprog/rox-multichild
pass tests/userprog/bad-read
pass tests/userprog/bad-write
pass tests/userprog/bad-read2
pass tests/userprog/bad-write2
pass tests/userprog/bad-jump
pass tests/userprog/bad-jump2
pass tests/vm/pt-grow-stack
pass tests/vm/pt-grow-pusha
pass tests/vm/pt-grow-bad
pass tests/vm/pt-big-stk-obj
pass tests/vm/pt-bad-addr
pass tests/vm/pt-bad-read
pass tests/vm/pt-write-code
pass tests/vm/pt-write-code2
pass tests/vm/pt-grow-stk-sc
pass tests/vm/page-linear
FAIL tests/vm/page-parallel     # suspected race condition
pass tests/vm/page-merge-seq
pass tests/vm/page-merge-par
pass tests/vm/page-merge-stk
pass tests/vm/page-merge-mm
pass tests/vm/page-shuffle
pass tests/vm/mmap-read
pass tests/vm/mmap-close
pass tests/vm/mmap-unmap
pass tests/vm/mmap-overlap
pass tests/vm/mmap-twice
pass tests/vm/mmap-write
pass tests/vm/mmap-exit
pass tests/vm/mmap-shuffle
pass tests/vm/mmap-bad-fd
pass tests/vm/mmap-clean
pass tests/vm/mmap-inherit
pass tests/vm/mmap-misalign
pass tests/vm/mmap-null
pass tests/vm/mmap-over-code
pass tests/vm/mmap-over-data
pass tests/vm/mmap-over-stk
pass tests/vm/mmap-remove
pass tests/vm/mmap-zero
pass tests/filesys/base/lg-create
pass tests/filesys/base/lg-full
pass tests/filesys/base/lg-random
pass tests/filesys/base/lg-seq-block
pass tests/filesys/base/lg-seq-random
pass tests/filesys/base/sm-create
pass tests/filesys/base/sm-full
pass tests/filesys/base/sm-random
pass tests/filesys/base/sm-seq-block
pass tests/filesys/base/sm-seq-random
pass tests/filesys/base/syn-read
pass tests/filesys/base/syn-remove
pass tests/filesys/base/syn-write
1 of 109 tests failed.

📂 Project 4 – File Systems (Partial Implementation)

Manual: Pintos Project 4

This extra credit project focused solely on file growth features, omitting full file system extensions due to time constraints.

🧭 Note: This project was not based on Project 3 (Virtual Memory). It was branched directly from the final state of Project 2, as it only required file system enhancements unrelated to virtual memory.

📌 Related Code

  • filesys/inode.c – Indexed inode (direct + single indirect), dynamic growth, and partial free logic

🔧 Check

git checkout project4
docker start -ai pintos

cd /root/pintos/src/filesys
make clean
make check
📋 Result

7 / 7 tests passed

pass tests/filesys/extended/grow-create
pass tests/filesys/extended/grow-file-size
pass tests/filesys/extended/grow-seq-lg
pass tests/filesys/extended/grow-seq-sm
pass tests/filesys/extended/grow-sparse
pass tests/filesys/extended/grow-tell
pass tests/filesys/extended/grow-two-files