, my concern was mainly about
Windows (which I know very little about), as there does not appear
to be a nanosecond or even microsecond alternative to
WaitForMultipleObjects. However, articles like this:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/e8a7cb1e-9edd-4ee3
-982e-f66b7bf6ae44/improve-accuracy-waitforsingleobject
suggest that WaitFor{Single,Multiple}Objects can have pretty
appalling latency anyway (100ms!), and there's no evidence that's
limited by making one of the FDs (or objects) ready.
... especially when making one of the FDs ready would likely have the
same latency in some internal Windows thread that implements timers.
In these
circumstances, I'd question whether we gain anything by worrying
about timer resolution.
Part of it should be fixed by os_setup_early_signal_handling.
This is corroborated by the fact that without
os_setup_early_signal_handling Wine always works, and Windows breaks.