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

diff --git a/TODO b/TODO
index d04e89d..e16216c 100644
--- a/TODO
+++ b/TODO
@@ -1,34 +1,117 @@
 -*- 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.
+* Test pintos with GSX.
 
-* The semantics of the join system call should change so that it only
-  returns the exit code once.
+* Need targets for checking single tests or single subdirs
 
-* mmap/munmap should use segment IDs like Nachos.  Too hard otherwise.
+  - `make check' should say how to get more information
 
-* Some confusion--do we really get overlapping ro/rw segment in normal
-  link?  Student example seemed to show that we don't.
+  - `make recheck', `make clean-check'
 
-* Finish writing the tour.
+* Need to put time limits on tests.
 
-* Come up with a way for us to release some of the tests.
+* Add a way for students to prints messages ignored by the autograder.
 
-* userprog project should mark read-only pages as actually read-only
-  in the page table
+  - Ignore text between /* and */.
 
-* Add src/testcases/vm, src/testcases/filesys and make it clear to use
-  them?
+  - Allow for a comment on `exit' lines?
 
-* Speed up disk routines: filling an 8 MB disk takes a long time.
+    . Get rid of LOAD_ERROR() macro by calling thread_exit() directly.
 
-* Not sure that raw arc4 should really be used so much in the tests.
-  Any reason not to use random_bytes()?
+* Improve automatic interpretation of exception messages.
 
-* Grading script patches needed anymore?
+* We need better and more example programs.
 
-* 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.
+  - Need an mmap example program as a replacement for the crappy mmap FAQ
+    question.
+
+  - How about `diff' and `cmp' programs?
+
+* Threads:
+
+  - mlfqs tests suck.  They aren't even correct, e.g. the amarv
+    submission from win0405 is graded incorrectly.
+
+* Userprog project:
+
+  - Don't emphasize that stuff needs to be copied from user space to
+    kernel space.  Instead, emphasize validation and suggest that
+    copying is a common solution and that it will be necessary in
+    project 3 and in real OSes.  Also revise the grading criteria to
+    match.
+
+  - 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.
+
+* VM project:
+
+  - Discuss the perils of mixing dirty bits between kernel and user virtual
+    memory.
+
+* Filesys project:
+
+  - Increase maximum disk size from 8 MB to something that actually
+    requires doubly indirect nodes.  There is a negative pressure here
+    from the bitmap object--perhaps we need a specialized bitmap that
+    doesn't have to be all in-memory at once.
+
+    Alternatively, shrink the inode size.
+
+  - Add option to disable buffer cache.
+
+  - Need a better way to measure performance improvement of buffer
+    cache.  Some students reported that their system was slower with
+    cache--likely, Bochs doesn't simulate a disk with a realistic
+    speed.
+
+  - Clarify effect of remove(cwd).
+
+* 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.
+
+  - GNU make 3.80 or later is required.
+
+* Assignments:
+
+  - Add extra credit:
+
+    . Low-level x86 stuff, like paged page tables.
+
+    . Specifics on how to implement sbrk, malloc.
+
+    . Other good ideas.
+
+    . opendir/readdir/closedir
+
+    . everything needed for getcwd()
+
+* Tests:
+
+  - 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.
+
+* Code:
+
+  - Need an optimization barrier and an explanation of it in the
+    documentation.
+
+  - Need to check the wait system call more thoroughly.