@section Tips
There should be no busy-waiting in any of your solutions to this
-assignment. Furthermore, resist the temptation to directly disable
-interrupts in your solution by calling @func{intr_disable} or
+assignment.
+
+Do your best to resist the temptation to directly disable interrupts
+in your solution by calling @func{intr_disable} or
@func{intr_set_level}, although you may find doing so to be useful
while debugging. Instead, use semaphores, locks and condition
variables to solve synchronization problems. Read the tour section on
-synchronization (@pxref{Synchronization}) or the comments
-in @file{threads/synch.h} if you're unsure what synchronization
+synchronization (@pxref{Synchronization}) or the comments in
+@file{threads/synch.h} if you're unsure what synchronization
primitives may be used in what situations.
Given some designs of some problems, there may be one or two instances
in which it is appropriate to directly change the interrupt levels
-instead of relying on the given synchroniztion primitives. This must
+instead of relying on the given synchronization primitives. This must
be justified in your @file{DESIGNDOC} file. If you're not sure you're
justified, ask!
the lock, then recall the donation once it has acquired the lock.
Implement this fix.
-You will need to account for all different orders that priority
+You will need to account for all different orders in which priority
donation and inversion can occur. Be sure to handle multiple
donations, in which multiple priorities are donated to a thread. You
must also handle nested donation: given high, medium, and low priority