🚀
Pintos
  • 🌈Welcome to Pintos
  • Getting Started
    • Environment Setup
    • Build and Run
      • Building Pintos
      • Running Pintos
    • Debug and Test
      • Testing
      • Debugging
    • Grading
  • Project Description
    • Lab0: Getting Real
      • Background
      • Your Tasks
      • FAQ
      • Submission
    • Lab1: Threads
      • Background
      • Suggestions
      • Your Tasks
      • FAQ
      • Submission
    • Lab2: User Programs
      • Background
      • Suggestions
      • Your Tasks
      • FAQ
      • Submission
    • Lab3a: Demand Paging
      • Background
      • Suggestions
      • Your Tasks
      • FAQ
      • Submission
    • Lab3b: Mmap Files
      • Your Tasks
      • FAQ
      • Submission
    • (Optional) Lab4: File Systems
      • Background
      • Suggestions
      • Your Tasks
      • FAQ
  • Appendix
    • Code Guide
      • Loading
      • Threads
      • Synchronization
      • Interrupt Handling
      • Memory Allocation
      • Virtual Addresses
      • Page Table
      • Hash Table
    • 4.4BSD Scheduler
    • C Standards
    • Project Documentation
    • Development Tools
    • Bibliography
  • Code Browser
Powered by GitBook
On this page
  • Development Suggestions
  • Suggested Order of Implementation
  1. Project Description
  2. Lab1: Threads

Suggestions

Development Suggestions

Your TAs find some tools very useful during the development, see Development Tools for details.

You should expect to (always) run into bugs that you simply don't understand while working on this and subsequent projects.

  • When you do, reread the appendix on debugging tools, which is filled with useful debugging tips that should help you to get back up to speed (see section Debugging).

  • Be sure to read the section on backtraces (see section Backtraces), which will help you to get the most out of every kernel panic or assertion failure.

Tips

We also suggest you read the Your Tasks as well as the FAQs carefully -- perhaps multiple times. A lot of the confusion comes from not reading them carefully.

Tips

make check runs all tests.

If you are debugging one test, you can run just that test with make tests/threads/<test_case>.result. Read the Testing part for more details.

Suggested Order of Implementation

We suggest first implementing the following, which can happen in parallel:

  • Optimized timer_sleep() in Exercise 1.1.

  • Basic support for priority scheduling in Exercise 2.1 when a new thread is created in thread_create().

  • Implement fixed-point real arithmetic routines (Fixed-Point Real Arithmetic) that are needed for MLFQS in exercise 3.1.

  • Then you can add full support for priority scheduling in Exercise 2.1 by considering all other possible scenarios and the synchronization primitives.

  • Then you can tackle either Exercise 3.1 first or Exercise 2.2 first.

PreviousBackgroundNextYour Tasks

Last updated 2 years ago