projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
30343d4
)
Mark test alarm-priority as timing-sensitive
author
John Ousterhout
<ouster@cs.stanford.edu>
Fri, 1 May 2020 23:56:30 +0000
(16:56 -0700)
committer
John Ousterhout
<ouster@cs.stanford.edu>
Tue, 12 May 2020 04:10:50 +0000
(21:10 -0700)
doc/threads.texi
patch
|
blob
|
history
diff --git
a/doc/threads.texi
b/doc/threads.texi
index bf8546e20526523a22fec5da30b76d68ddf9364a..c9094bc2d073ddd5642aad218fc82465ecabdc5c 100644
(file)
--- a/
doc/threads.texi
+++ b/
doc/threads.texi
@@
-648,7
+648,8
@@
to cause many of the tests to fail.
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
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-simultaneous},
+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.,
@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.,