Get rid of THREAD_JOIN_IMPLEMENTED by adding thread_join() stub.

[pintos-anon] / doc / vm.texi

diff --git a/doc/vm.texi b/doc/vm.texi
index 599539be86b905cfa54a071a34122cd69097e86a..fe948207486f56800d8ae81010bc6ede91e1de3e 100644 (file)
--- a/doc/vm.texi
+++ b/doc/vm.texi
@@ -38,9 +38,6 @@ introduced in this project.
 You will continue to handle Pintos disks and file systems the same way
 you did in the previous assignment (@pxref{Using the File System}).
 
-Your submission should define @code{THREAD_JOIN_IMPLEMENTED} in
-@file{constants.h} (@pxref{Conditional Compilation}).
-
 @menu
 * VM Design::                   
 * Page Faults::                 
@@ -256,9 +253,7 @@ It is impossible to predict how large the stack will grow at compile
 time, so we must allocate pages as necessary.  You should only allocate
 additional pages if they ``appear'' to be stack accesses.  You must
 devise a heuristic that attempts to distinguish stack accesses from
-other accesses.@footnote{You might find it useful to know that the
-80@var{x}86 instruction @code{pusha} pushes all 8 registers (32 bytes)
-on the stack at once.}  Document and explain the heuristic in your
+other accesses.  Document and explain the heuristic in your
 design documentation.
 
 The first stack page need not be loaded lazily.  You can initialize it