Rockbox

This just takes Slasheri's scheduler boost control and makes it (I think) more generally applicable -- the thread scheduler tracks how many threads have requested scheduler managed boosting, removing a thread from that boosted set whenever that thread goes to sleep (BUT not when that thread blocks w/o a timeout). Based on this boosted thread count, the thread scheduler boosts and unboosts the CPU.

I think that this type of boosting can be used to simplify coding with boost, for plugin authors and anyone else. For an interactive plugin, it would be as easy as calling the trigger_cpu_boost function and forgetting about it, because the next time you wait for user input, the CPU will unboost itself.

http://lostlogicx.com/transfer/rockbox/scheduler_boost_ctrl_enhanced.patch