146f113fec
potentially want to notify the profiler thread (i.e. wake it up), which can cause another scheduling event notification. That is we have to make sure that event buffer is in a consistent state at that point (i.e. wake up the thread at the very end of the callbacks). Furthermore the ThreadEnqueuedInRunQueue() callback can be called with spinlocks besides the thread spinlock being held. In particular waking up threads also happens in the condition variable code with a static spinlock being held. Trying to notify the condition variable the profiler thread is waiting on in such a case would be a guaranteed deadlock. Hence we avoid doing that, now. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30339 a95241bf-73f2-0310-859d-f6bbb57e9c96 |
||
---|---|---|
.. | ||
boot | ||
glue | ||
kernel | ||
ldscripts | ||
libroot | ||
runtime_loader | ||
Jamfile |