Skip to content

Prep: Setup and Hello, Rust — 00r

Session: Thu Aug 27, 1h45 · Exercises: 00r_hello_rust · Prep time: ~30 min · Lecture: Week 1 · Building an Operating System, and Your First Rust

Most of Thursday is setup. Work the Setup page step by step: accept both GitHub invitations, clone your repo, toolchain, oslings doctor green, first oslings submit. Budget 45 minutes.

What you will build

Your first Rust, and the number formats the kernel is written in. You will name a couple of values a kernel keeps returning to — a page size, the address the kernel is linked at — the way kernel source writes them: hexadecimal, grouped with underscores, integer type spelled out. Then a function or two whose whole body is one expression. Nothing boots; the check is plain cargo test on your machine, green when the constants hold the exact values the lecture quotes and the functions return what the tests expect.

Concepts you need

Read before class

What Time
Setup 8 min
Week 1 · This week, then Thursday · 00r Hello, Rust, all five sections 8 min
Week 1 · How the Course Runs: the classroom network, the three commands, and what earns credit 3 min
Week 1 · For the exam: Octal, and four spellings of one number, as truncates and Hex by hand. Not needed today; on Midterm 1 2 min
Dev Setup guide: Install rustup, Accept your two invitations and oslings doctor 5 min
Using OSlings guide: The three test modes 2 min

Have done before Thursday:

  • rustup installed and rustc --version working (Dev Setup guide: Install rustup); large download.
  • A GitHub account, and know which one you are signed in as. Your oslings-<username> repository is created for you — you do not make one. Accepting the two invitations is Setup step 3, and you can do it at home.
  • A charged computer running macOS, Linux, or Windows with WSL2.

Mental model

const UART0: usize = 0x1000_0000;   // an address: usize, hex, grouped in fours
const LSR_THRE: u8 = 1 << 5;        // bit 5 of one 8-bit device register

fn can_send(status: u8) -> bool {
    status & LSR_THRE != 0          // no semicolon: this is the value
}
// can_send(0b0010_0000) == true      can_send(0x00) == false

Every line is a decision the hardware already made. 0x1000_0000 is where QEMU puts the serial port; hex shows it is one bit twenty-eight places up. u8 is the register's width, so a read is a one-byte bus transaction, not four. The body of can_send is one expression with no semicolon; put one there and the function returns (), and the compiler says "expected bool, found ()". Today's exercise is this pattern with different numbers; in 31k_boot such constants become the kernel's real memory map.

Check yourself

  1. What is 0x1000 in decimal, and how can you tell without dividing that 0x8000_0000 is a multiple of it?
    Answer4096; one hex digit is four bits, so 0x1000 is one bit at position 12. A hex numeral ending in three zeros has its low twelve bits clear, so it is a multiple of 0x1000, as a decimal ending in 000 is a multiple of 1000.
  2. What does the compiler say about fn twice(x: u64) -> u64 { x * 2; }, and what is the fix?
    Answererror[E0308]: mismatched types, expected u64, found (). The semicolon discards the value; delete it, or write return x * 2;.
  3. Pick the type and binding form: a memory address, a UART register, a free-page count that goes down.
    Answerusize, u8, and let mut on a usize: bindings are immutable by default, so a value that changes must say so.

What "done" looks like

oslings run is green, then oslings submit before you leave. Not green? Submit anyway — the tests that pass earn their share — then finish it at a make-up session (office hours, on the class network) for three quarters, or anywhere else for half, and submit again.

Today "done" also means the Setup deliverables are checked off and the commit is visible on github.com.

If you finish early