From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53796) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEMtJ-00025z-6V for qemu-devel@nongnu.org; Wed, 19 Sep 2012 12:12:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEMtE-0005B2-QU for qemu-devel@nongnu.org; Wed, 19 Sep 2012 12:12:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55661) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEMtE-0005Af-IP for qemu-devel@nongnu.org; Wed, 19 Sep 2012 12:12:40 -0400 Message-ID: <5059EEED.7040405@redhat.com> Date: Wed, 19 Sep 2012 18:12:29 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1348000626-16129-1-git-send-email-aliguori@us.ibm.com> <5059738E.5070004@redhat.com> <5059ED2B.3090609@weilnetz.de> In-Reply-To: <5059ED2B.3090609@weilnetz.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] qemu-clock: add an alarm timer based on timerfd List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: Jan Kiszka , Anthony Liguori , qemu-devel@nongnu.org, Peter Portante Il 19/09/2012 18:04, Stefan Weil ha scritto: > The win32 timer still works when these modifications were applied. > What are they good for? IIUC the Win32 did _not_ work (except on Wine) without these. Note I'm talking about "-clock win32". So these provide a hint that the problem with the Win32 timer is not in the bowels of Windows, but only that it does not adjust the Windows scheduler quantum. Wine does not need it because the Linux scheduler is not as lame. So if we just eliminated timers and used the g_poll timeout (what was proposed upthread), Windows would work provided timeBeginPeriod/timeEndPeriod are called correctly. Paolo