X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=TODO;h=15902a2cd3db19fd7e77209b9d82127190a96759;hb=5b670fb86ef37f5a81188e940e5fe1b04b5824af;hp=30f324682f09fc10a05eacd400ad8f1fa1ae6422;hpb=ff076af15fa93292b8843e76bd6bab7ac5421095;p=pintos-anon diff --git a/TODO b/TODO index 30f3246..15902a2 100644 --- a/TODO +++ b/TODO @@ -1,30 +1,56 @@ -*- 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. +* Userprog project: -* The semantics of the join system call should change so that it only - returns the exit code once. + - Move `join' implementation here, from `threads' project, to help + normalize the project difficulties. -* mmap/munmap should use segment IDs like Nachos. Too hard otherwise. + - The semantics of the join system call should change so that it + only returns the exit code once. -* Some confusion--do we really get overlapping ro/rw segment in normal - link? Student example seemed to show that we don't. + - 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. -* Finish writing the tour. + - 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. -* Come up with a way for us to release some of the tests. +* Documentation: -* userprog project should mark read-only pages as actually read-only - in the page table + - Finish writing tour. -* Add src/testcases/vm, src/testcases/filesys and make it clear to use - them? + - Add "Digging Deeper" sections that describe the nitty-gritty x86 + details for the benefit of those interested. -* Speed up disk routines: filling an 8 MB disk takes a long time. + - Add explanations of what "real" OSes do to give students some + perspective. -* Not sure that raw arc4 should really be used so much in the tests. - Any reason not to use random_bytes()? +* 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. -* Grading script patches needed anymore?