From: Ben Pfaff Date: Wed, 6 Oct 2004 21:28:34 +0000 (+0000) Subject: Fix wording. X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a735930b337c32c28e7641401f47999845adba78;p=pintos-anon Fix wording. --- diff --git a/doc/threads.texi b/doc/threads.texi index f219db4..74f51bc 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -462,9 +462,8 @@ When a thread is added to the ready list that has a higher priority than the currently running thread, the current thread should immediately yield the processor to the new thread. Similarly, when threads are waiting for a lock, semaphore or condition variable, the -highest priority waiting thread should be woken up first. A thread's -priority may be set at any time, including while the thread is waiting -on a lock, semaphore, or condition variable. +highest priority waiting thread should be woken up first. A thread +may set its priority at any time. One issue with priority scheduling is ``priority inversion'': if a high priority thread needs to wait for a low priority thread (for