Each discussion section is conducted by a TA. Below is a list showing which TA is responsible for which discussion section:

• Fri 10:00am - 10:50am in (Bill Cheng)
• Fri 11:00am - 11:50am in (TBD)
• Fri 12:00pm - 12:50pm in (TBD)

During a discussion section, the TA will primarily present information regrading up-coming programming assignments. If you have a particular topic that you would like the TA to discuss in class (including stuff like something covered in lectures that you would like the TA to explain further), you should send e-mail to the TA before 5PM on Thursday. The TA will try his/her best to cover such requests.

Please note that programming assignments are due on Tuesdays. Since you are expected to have finished the an assignment before its due date, on the due date of a programming assignment, the TA will be introducint the next programming assignment and that takes priority over the current assignment. If there is time left, the TA can discuss the current assignment.

The following are tentative and final slides (in PDF format) for this semester. Please note that the source code below is for the purpose of discussions and may not be identical to the code in your assignments. It would be a really bad idea (because you can lose a lot of points) to replace the code in your assignments with the code here!

• Week 1 (PDF) (6-up PDF) - gdb, warmup #1
• Week 2 (PDF) (6-up PDF) - C, Unix
• Week 3 (PDF) (6-up PDF) - warmup #2 introduction
• Week 4 (PDF) (6-up PDF) - warmup #2, multiple processes and multiple threads

  Code in slides:

  • defs.h
  • fork-wait.c
  • cat.c
  • redirect.c
  • thr-term.c
  • busywait.c
  • join.c
  • deadlock.c
  • trylock.c
  • whoopee.c
  • status-update.c
  • sigblock.c
  • sigwait.c
  • direct.c
  • cancel.c
  • three-threads.c

• Week 5 (PDF) (6-up PDF) - introduction to kernel assignments
• Week 6 (PDF) (6-up PDF) - kernel 1

  Code:

  • kmain.c

• Week 7 (PDF) (6-up PDF) - faber_test, kernel 1 FAQ

  Code:

  • week6.csh
  • faber_test.c

• Week 8 (PDF) (6-up PDF) - faber_test, kernel 1 FAQ, introduction to kernel 2

  Code:

  • faber_test.c

• Week 9 - kernel 2, polymorphism

  Notes:

  • week9-notes.txt

  Code:

  • namev.c (path name resolution code)
  • vnode.c
  • ramfs.c (also look for any "_ops_t" in "kernel/include/fs/*.h", "kernel/fs/*.c" and "kernel/fs/ramfs/*.c")

• Week 10 - kernel 2, ramfs.c vfstest.c, faber_fs_test

  Code:

  • week8.csh
  • ramfs.c
  • vfs_syscall.c
  • vfstest.c
  • faber_fs_test.c

• Week 11 (PDF) (6-up PDF) - introduction to kernel 3
• Week 12 (PDF) (6-up PDF) - address space implementation (vmarea, mmobj, pframe, page table), page fault handling, objdump, kernel 3 FAQ, hello

  Code (user):

  • hello.c

  Code (kernel):

  • exec.c - how to go into user space
  • elf32.c - the loader
  • vn_mmobj_ops.c - code for the mmobj inside a vnode
  • access.c - need to understand copy_from_user() and copy_to_user()
  • syscall.c - to see how to implement sys_write(), look at how other sys_*() functions are implemented

• Week 13 - objdump, kernel 3 FAQ, hello

  Code (user):

  • hello.c
  • syscall.c (user space)

  Useful commands:

      objdump --disassemble --section=".text" user/usr/bin/hello.exec
      objdump --disassemble --section=".text" -S user/usr/bin/hello.exec
      objdump --headers user/usr/bin/hello.exec
      xxd -g 1 user/usr/bin/hello.exec

• Week 14 - fork-and-wait, do_fork(), user space shell, do_brk(), memtest, eatmem, forkbomb, kernel 3 FAQ

  Code (user):

  • fork-and-wait.c, init.c
  • memtest.c, eatmem.c, forkbomb.c

• Week 15 - (no discussion section this week)

Week #	Date	Topics	Comments
1	1/17	gdb, warmup #1
2	1/24	C, Unix
3	1/31	warmup #2	(warmup #1 due at end of day)
4	2/7	multithreading & Unix signals
5	2/14	intro to kernel assignments
6	2/21	introduction to kernel #1	(warmup #2 due at end of day)
7	2/28	faber_test
8	3/6	more faber_test, introduction to kernel #2
9	3/13	polymorphism, reference counting	(kernel #1 due at end of day)
10	3/27	vfstest, faber_fs_test
11	4/3	introduction to kernel #3
12	4/10	objdump, address space implementation, hello	(kernel #2 due at end of day)
13	4/17	fork, user space shell
14	4/24	brk, memtest, eatmem, forkbomb
15	5/1	(no discussion section this week)	(kernel #3 due at end of day)