X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=TODO;h=53a7060081310488bf1d7f47e4722f2aba11f4cf;hb=edb2693ddd1f451e190a81da0ddda4df845fb246;hp=40c15e7d9c10da4a40efd23a0cedbc6b7934bbcb;hpb=cdc1ff02d0f3a0d57cd41e9794d26b62bfc65015;p=pintos-anon diff --git a/TODO b/TODO index 40c15e7..53a7060 100644 --- a/TODO +++ b/TODO @@ -1,7 +1,5 @@ -*- text -*- -* Bochs is not fully reproducible. - Godmar says: - In Project 2, we're missing tests that pass arguments to system calls @@ -28,46 +26,6 @@ Add a system call "get_kernel_memory_information". User programs could engage in a variety of activities and notice leaks by checking the kernel memory statistics. ---- - -From: "Godmar Back" -Subject: priority donation tests -To: "Ben Pfaff" -Date: Fri, 3 Mar 2006 11:02:08 -0500 - -Ben, - -it seems the priority donation tests are somewhat incomplete and allow -incorrect implementations to pass with a perfect score. - -We are seeing the following wrong implementations pass all tests: - -- Implementations that assume locks are released in the opposite order -in which they're acquired. The students implement this by -popping/pushing on the donation list. - -- Implementations that assume that the priority of a thread waiting on -a semaphore or condition variable cannot change between when the -thread was blocked and when it is unblocked. The students implement -this by doing an insert into an ordered list on block, rather than -picking the maximum thread on unblock. - -Neither of these two cases is detected; do you currently check for -these mistakes manually? - -I wrote a test that checks for the first case; it is here: -http://people.cs.vt.edu/~gback/pintos/priority-donate-multiple-2.patch - -[...] - -I also wrote a test case for the second scenario: -http://people.cs.vt.edu/~gback/pintos/priority-donate-sema.c -http://people.cs.vt.edu/~gback/pintos/priority-donate-sema.ck - -I put the other tests up here: -http://people.cs.vt.edu/~gback/pintos/priority-donate-multiple2.c -http://people.cs.vt.edu/~gback/pintos/priority-donate-multiple2.ck - From: "Godmar Back" Subject: multiple threads waking up at same clock tick To: "Ben Pfaff" @@ -205,17 +163,10 @@ Godmar Back writes: * Finish writing tour. -* Introduce a "yield" system call to speed up the syn-* tests. - via Godmar Back: -* Project 3 solution needs FS lock. - * Get rid of mmap syscall, add sbrk. -* Make backtrace program accept multiple object file arguments, - e.g. add -u option to allow backtracing user program also. - * page-linear, page-shuffle VM tests do not use enough memory to force eviction. Should increase memory consumption.