X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fthreads.texi;h=c9094bc2d073ddd5642aad218fc82465ecabdc5c;hb=9f013d0930202eea99c21083b71098a0df64be0d;hp=c1f3bfcd62c2caf43a0b1cbf1118b0cf8ffdb62f;hpb=a03618133f7df0954802a470a4bee7674f7aed45;p=pintos-anon

diff --git a/doc/threads.texi b/doc/threads.texi
index c1f3bfc..c9094bc 100644
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -643,6 +643,18 @@ to cause many of the tests to fail.
 
 @xref{Testing}.
 
+@item Should I try running the tests with jitter?
+
+Using the jitter feature in Bochs (@pxref{Debugging versus Testing})
+is a great way to discover bugs that are timing dependent. However,
+the following tests are known to
+fail with jitter even if your code is correct: @code{alarm-priority},
+@code{alarm-simultaneous},
+@code{mlfqs-recent-1}, @code{mlfqs-fair-2}, @code{mlfqs-fair-20},
+@code{mlfqs-nice-2}, @code{mlfqs-nice-10}, and @code{priority-fifo}.
+The behavior of these tests can sometimes vary based on timing (e.g.,
+if a timer interrupt arrives at an inconvenient time).
+
 @item Why do I get a test failure in @func{pass}?
 
 @anchor{The pass function fails}
@@ -726,7 +738,7 @@ kernel thread but the first.
 Don't worry about the possibility of timer values overflowing.  Timer
 values are expressed as signed 64-bit numbers, which at 100 ticks per
 second should be good for almost 2,924,712,087 years.  By then, we
-expect Pintos to have been phased out of the @value{coursenumber} curriculum.
+expect Pintos to have been phased out of the Computer Science curriculum.
 @end table
 
 @node Priority Scheduling FAQ