From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47190) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rowbh-0005x0-8g for qemu-devel@nongnu.org; Sun, 22 Jan 2012 07:33:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rowbg-0004L8-76 for qemu-devel@nongnu.org; Sun, 22 Jan 2012 07:33:13 -0500 Received: from lo.gmane.org ([80.91.229.12]:53289) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rowbg-0004Ku-0k for qemu-devel@nongnu.org; Sun, 22 Jan 2012 07:33:12 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Rowbe-0001b9-4J for qemu-devel@nongnu.org; Sun, 22 Jan 2012 13:33:10 +0100 Received: from 93-34-200-238.ip51.fastwebnet.it ([93.34.200.238]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jan 2012 13:33:10 +0100 Received: from pbonzini by 93-34-200-238.ip51.fastwebnet.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jan 2012 13:33:10 +0100 From: Paolo Bonzini Date: Sun, 22 Jan 2012 13:32:56 +0100 Message-ID: References: <1327108107-16600-1-git-send-email-mdroth@linux.vnet.ibm.com> <1327166033-17922-1-git-send-email-mdroth@linux.vnet.ibm.com> <20120121203923.GE4871@jl-vm1.vm.bytemark.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <20120121203923.GE4871@jl-vm1.vm.bytemark.co.uk> Subject: Re: [Qemu-devel] [PATCH] main-loop: For tools, initialize timers as part of qemu_init_main_loop() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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 Paolo