AD Controls Department » Front-end Group » Infrastructure » MOOC Framework

Early MOOC authors used intLock/intUnlock and taskLock/taskUnlock as quick-n-dirty ways to provide serialization. These primitives add latency to interrupts and context switches, respectively. It's inappropriate affecting other tasks and interrupts because someone was too lazy to properly serialize the data structures. To close this issue, we need:

• A global MOOC mutex to provide atomic changes to MOOC internals.
• All intLock/intUnlock and taskLock/taskUnlock instances should be converted to semTake/semGive calls.
• Bonus points for finding and fixing other areas that weren't properly protected¹.

It should be noted that MOOC drivers can have a mutex associated with their instance, so care must be taken to ensure there's no possibility of deadlock in using these mutexes.

¹ For instance, the multiple RETDAT tasks transfer packets to the RETDAT reply task and there's some slop in there because we couldn't guarantee things were happening atomically. This can now be fixed.