-*- text -*-
-* The p1-4.c testcase needs significant tuning. Currently it takes
- too long (especially when SHOW_PROGRESS is turned on) and doesn't
- show significant improvement.
+* Miscellaneous:
-* The semantics of the join system call should change so that it only
- returns the exit code once.
+ - Currently the `pintos' utility has a broken return code policy: it
+ returns 1 to indicate success. It inherited this mistake from
+ Bochs, which does something similar. This needs to be fixed.
-* mmap/munmap should use segment IDs like Nachos. Too hard otherwise.
+* Userprog project:
+
+ - Move `join' implementation here, from `threads' project, to help
+ normalize the project difficulties.
+
+ - The semantics of the join system call should change so that it
+ only returns the exit code once.
+
+ - Mark read-only pages as actually read-only in the page table. Or,
+ since this was consistently rated as the easiest project by the
+ students, require them to do it.
+
+ - Don't provide per-process pagedir implementation but only
+ single-process implementation and require students to implement
+ the separation? This project was rated as the easiest after all.
+ Alternately we could just remove the synchronization on pid
+ selection and check that students fix it.
+
+* Documentation:
+
+ - Finish writing tour.
+
+ - Add "Digging Deeper" sections that describe the nitty-gritty x86
+ details for the benefit of those interested.
+
+ - Add explanations of what "real" OSes do to give students some
+ perspective.
+
+* Assignments:
+
+ - Add extra credit:
+
+ . Low-level x86 stuff, like paged page tables.
+
+ . Other good ideas.
+
+ - mmap/munmap should use segment IDs like Nachos. Too hard
+ otherwise.
+
+ - Add src/testcases/vm, src/testcases/filesys and make it clear to use
+ them?
+
+* Tests:
+
+ - Release some of them.
+
+ - The threads, userprog, vm test source files could use
+ factorization and cleanup along the lines of fslib in the filesys
+ tests.
+
+ - The p1-4.c testcase needs significant tuning. Currently it takes
+ too long (especially when SHOW_PROGRESS is turned on) and doesn't
+ show significant improvement.
-* Some confusion--do we really get overlapping ro/rw segment in normal
- link? Student example seemed to show that we don't.