From: Ben Pfaff <blp@cs.stanford.edu>
Date: Mon, 11 Oct 2004 22:45:47 +0000 (+0000)
Subject: Adjust wording of "static priority" comment.
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e165d8f26d62602d925c156b162103efb3292a5e;p=pintos-anon

Adjust wording of "static priority" comment.
---

diff --git a/doc/threads.texi b/doc/threads.texi
index e5b087b..1e37971 100644
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -490,6 +490,10 @@ for a lock held by a lower-priority thread.  You do not need to
 implement this fix for semaphores, condition variables or joins.
 However, you do need to implement priority scheduling in all cases.
 
+You may assume a static priority for priority donation, that is, it is
+not necessary to ``re-donate'' a thread's priority if it changes
+(although you are free to do so).
+
 @node Problem 1-4 Advanced Scheduler
 @section Problem 1-4: Advanced Scheduler
 
@@ -503,10 +507,6 @@ relative to the original Pintos scheduling algorithm (round robin) for
 at least one workload of your own design (i.e.@: in addition to the
 provided test).
 
-You may assume a static priority for this problem. It is not necessary
-to ``re-donate'' a thread's priority if it changes (although you are
-free to do so).
-
 You must write your code so that we can turn the MLFQS on and off at
 compile time.  By default, it must be off, but we must be able to turn
 it on by inserting the line @code{#define MLFQS 1} in