Andrew Eikum asked:
>Is it true that SetEvent() causes a context switch?
Looking at +tid log files, I've seen switches happen after SetEvent
often enough. That motivated some changes to winmm notification in
the last years, i.e. call SetEvent after all local work is finished
and objects are in a
On Thu, Dec 20, 2012 at 02:03:06PM +0100, joerg-cyril.hoe...@t-systems.com
wrote:
> what's up with this patch?
>
> I wrote:
> >SetEvent is one of those calls with a high probability that the
> >Linux scheduler will switch to another thread, e.g. the one receiving
> >the event. As the critical se
Hi,
what's up with this patch?
I wrote:
>SetEvent is one of those calls with a high probability that the
>Linux scheduler will switch to another thread, e.g. the one receiving
>the event. As the critical section is still hold, it'll prevent the
>receiver from invoking mmdevapi, e.g. GetCurrentPa
