X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=TODO;h=a07e2b422e21fe45b32a9f4cb5dc37c3ceb297b7;hb=4eebaacd20c4d3bcc440751acdb8149ff9e56c11;hp=d04e89d8b0aa9d2cb47efbec44c102b5cebdc2a3;hpb=a3c7056dd123d3b0642bcbecddc7e6d1f9535867;p=pintos-anon

diff --git a/TODO b/TODO
index d04e89d..a07e2b4 100644
--- a/TODO
+++ b/TODO
@@ -1,34 +1,62 @@
 -*- 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.
+* Clean up:
 
-* The semantics of the join system call should change so that it only
-  returns the exit code once.
+  - Replace AT&T assembly code by Intel assembly so that students can
+    figure out the asm from the Intel manuals.  Compare object files
+    before and after to make sure nothing changed.
 
-* mmap/munmap should use segment IDs like Nachos.  Too hard otherwise.
+* Userprog project:
 
-* Some confusion--do we really get overlapping ro/rw segment in normal
-  link?  Student example seemed to show that we don't.
+  - Move `join' implementation here, from `threads' project, to help
+    normalize the project difficulties.
 
-* Finish writing the tour.
+  - The semantics of the join system call should change so that it
+    only returns the exit code once.
 
-* Come up with a way for us to release some of the tests.
+  - 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.
 
-* userprog project should mark read-only pages as actually read-only
-  in the page table
+  - 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.
 
-* Add src/testcases/vm, src/testcases/filesys and make it clear to use
-  them?
+* Documentation:
 
-* Speed up disk routines: filling an 8 MB disk takes a long time.
+  - Finish writing tour.
 
-* Not sure that raw arc4 should really be used so much in the tests.
-  Any reason not to use random_bytes()?
+  - Add "Digging Deeper" sections that describe the nitty-gritty x86
+    details for the benefit of those interested.
 
-* Grading script patches needed anymore?
+  - 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.
 
-* Add a "real-time" option to `pintos' script so that 30 second
-  intervals can be accurately timed for HW#1 timer, HW#4 write-behind
-  cache.