From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] main-loop: For tools, initialize timers as part of qemu_init_main_loop()
Date: Sun, 22 Jan 2012 13:32:56 +0100 [thread overview]
Message-ID: <jfgvlp$adk$1@dough.gmane.org> (raw)
In-Reply-To: <20120121203923.GE4871@jl-vm1.vm.bytemark.co.uk>
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 <pbonzini@redhat.com>
Paolo
next prev parent reply other threads:[~2012-01-22 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 1:08 [Qemu-devel] [PATCH] main-loop: Fix SetEvent() on uninitialized handle on win32 Michael Roth
2012-01-21 7:49 ` Paolo Bonzini
2012-01-21 17:13 ` [Qemu-devel] [PATCH] main-loop: For tools, initialize timers as part of qemu_init_main_loop() Michael Roth
2012-01-21 20:39 ` Jamie Lokier
2012-01-22 12:32 ` Paolo Bonzini [this message]
2012-01-23 0:12 ` Michael Roth
2012-01-23 7:49 ` Paolo Bonzini
2012-01-27 5:46 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-01-27 8:09 ` Paolo Bonzini
2012-01-27 5:46 ` Stefan Hajnoczi
2012-02-01 22:10 ` [Qemu-devel] " Anthony Liguori
2012-01-27 5:41 ` [Qemu-devel] [Qemu-trivial] [PATCH] main-loop: Fix SetEvent() on uninitialized handle on win32 Stefan Hajnoczi
2012-01-27 14:52 ` [Qemu-devel] [PATCH v2] " Michael Roth
2012-02-01 22:10 ` [Qemu-devel] [PATCH] " Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jfgvlp$adk$1@dough.gmane.org' \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).