From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56915) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1xFc-0001Pc-Op for qemu-devel@nongnu.org; Wed, 24 Jul 2013 07:29:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1xFb-0006fB-Qc for qemu-devel@nongnu.org; Wed, 24 Jul 2013 07:29:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39575) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1xFb-0006f0-Bd for qemu-devel@nongnu.org; Wed, 24 Jul 2013 07:28:59 -0400 Message-ID: <51EFBA57.6020409@redhat.com> Date: Wed, 24 Jul 2013 13:28:23 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1374396185-10870-1-git-send-email-pingfank@linux.vnet.ibm.com> <429B80A9A0DBF7FBF05E7C5A@nimrod.local> <628DFBF37B094813C72B6DBF@Ximines.local> <51EE5B34.10507@redhat.com> <51EF7752.9020505@redhat.com> <11E9299201E9A8D837D212DB@nimrod.local> <51EF85A0.6070307@redhat.com> <0C1B02FD6461BD119735B002@nimrod.local> <7A0F4F924E5E5BEE3070A41B@nimrod.local> In-Reply-To: <7A0F4F924E5E5BEE3070A41B@nimrod.local> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 0/8] arm AioContext with its own timer stuff List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Bligh Cc: Kevin Wolf , Stefan Hajnoczi , Jan Kiszka , liu ping fan , qemu-devel@nongnu.org, Anthony Liguori Il 24/07/2013 10:37, Alex Bligh ha scritto: > > > --On 24 July 2013 09:01:22 +0100 Alex Bligh wrote: > >>>> Most 'reasonable' POSIX compliant operating systems have ppoll >>> >>> Really? I could find no manpages for any of Solaris and *BSD. >> >> OK I shall (re)research that then! I suppose select() / pselect() is >> an alternative when there are few FDs. > > Looks like I was wrong. However, pselect support is pretty wide. Yes, on the other hand we only recently switched from select() to poll(). I guess using ms resolution wouldn't be too bad for non-Linux. After all before dynticks support was added to the alarm timer, it used to use /dev/rtc or /dev/hpet -- which is very precise but only has ms resolution too. We might not care about the slack either, in practice. TCG timing sucks anyway, and for KVM/Xen most relevant device models are in the kernel. Paolo