From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VLxzx-0005xx-IY for qemu-devel@nongnu.org; Tue, 17 Sep 2013 12:19:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VLxzr-0000XF-JG for qemu-devel@nongnu.org; Tue, 17 Sep 2013 12:19:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43553) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VLxzr-0000X9-9b for qemu-devel@nongnu.org; Tue, 17 Sep 2013 12:19:27 -0400 Message-ID: <5238810E.1050304@redhat.com> Date: Tue, 17 Sep 2013 18:19:26 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1376239405-4084-1-git-send-email-alex@alex.org.uk> <520A2511.4000709@siemens.com> <307AE3B5-FAFE-4E9C-A336-092245809528@alex.org.uk> <520A33B4.9030207@siemens.com> <14A27B81-C9FD-4EE5-BC4A-7106CD70527A@alex.org.uk> <520A3888.9020307@siemens.com> <20130813142204.GA3008@stefanha-thinkpad.redhat.com> <52387EC2.6000502@siemens.com> In-Reply-To: <52387EC2.6000502@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] [PATCHv10 00/31] aio / timers: Add AioContext timers and use ppoll List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Kevin Wolf , Anthony Liguori , Stefan Hajnoczi , Stefan Hajnoczi , qemu-devel@nongnu.org, liu ping fan , Alex Bligh , MORITA Kazutaka , rth@twiddle.net Il 17/09/2013 18:09, Jan Kiszka ha scritto: > On 2013-08-13 16:22, Stefan Hajnoczi wrote: >> On Tue, Aug 13, 2013 at 03:45:44PM +0200, Jan Kiszka wrote: >>> Yeah: >>> >>> - /* No AIO operations? Get us out of here */ >>> - if (!busy) { >>> + /* early return if we only have the aio_notify() fd */ >>> + if (ctx->pollfds->len == 1) { >>> return progress; >>> } >>> >>> So this is even worse for my use case. >> >> We can change the semantics of aio_poll() so long as we don't break >> existing callers and tests. It would make sense to do that after >> merging the io_flush and AioContext timers series. > > Need to pick up this topic again because above change is now mainline > and breaks aio_poll-based timer threads: > > How can we make progress with overcoming that check, at least for the > timer thread use case? Additional argument "truly_block" for aio_poll? I wonder if we still need that "if" at all. Guys, do you remember what it is good for? O:-) Paolo