On 01/21/2012 09:39 PM, Jamie Lokier wrote:
Is this a timer that need to fire soon after setting, every time?
I wonder if a different kind of Windows timer, lower-resolution, could
be used if the timeout is longer. If it has insufficient resolution,
it could be set to trigger a little early, then set a high-resolution
timer at that point.
Maybe that could help for Linux CONFIG_NOHZ guests?
No, it's an implementation detail of Windows multimedia timers. Just
enabling them apparently burns CPU.
There is another kind of timers for Windows but it didn't work reliably.
Finding out why would be the right fix, but anyway
Reviewed-by: Paolo Bonzini <pbonz...@redhat.com>
Paolo
