Footnotes

(1)

The term `uname -m` expands to a value such as x86_64 that indicates the type of computer you're logged into.

(2)

GDB might tell you that schedule() doesn't exist, which is arguably a GDB bug. You can work around this by setting the breakpoint by filename and line number, e.g. break thread.c:ln where ln is the line number of the first declaration in schedule().

(3)

We will treat these terms as synonyms. There is no standard distinction between them, although Intel processor manuals make a minor distinction between them on 80x86.

(4)

This rule is common but not universal. One modern exception is the x86-64 System V ABI, which designates 128 bytes below the stack pointer as a "red zone" that may not be modified by signal or interrupt handlers.

(5)

This is because switch_threads() takes arguments on the stack and the 80x86 SVR4 calling convention requires the caller, not the called function, to remove them when the call is complete. See [ SysV-i386] chapter 3 for details.

(6)

Actually, virtual to physical translation on the 80x86 architecture occurs via an intermediate "linear address," but Pintos (and most modern 80x86 OSes) set up the CPU so that linear and virtual addresses are one and the same. Thus, you can effectively ignore this CPU feature.

(7)

Because we are working in binary, the "decimal" point might more correctly be called the "binary" point, but the meaning should be clear.

(8)

pintos-gdb is a wrapper around gdb (80x86) or i386-elf-gdb (SPARC) that loads the Pintos macros at startup.

(9)

To be precise, GDB will stop only when running under Bochs. When running under QEMU, you must set a breakpoint in the page_fault function to stop execution when a page fault occurs. In that case, the btpagefault macro is unnecessary.

(10)

This is typically vi. To exit vi, type : q Enter.