From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V75uI-00045U-Ds for qemu-devel@nongnu.org; Wed, 07 Aug 2013 11:44:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V75uD-0006UM-Dd for qemu-devel@nongnu.org; Wed, 07 Aug 2013 11:44:14 -0400 Received: from mx3-phx2.redhat.com ([209.132.183.24]:41067) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V75uD-0006TU-5X for qemu-devel@nongnu.org; Wed, 07 Aug 2013 11:44:09 -0400 Date: Wed, 7 Aug 2013 11:43:58 -0400 (EDT) From: Paolo Bonzini Message-ID: <1242198191.10821363.1375890238185.JavaMail.root@redhat.com> In-Reply-To: <20130806153857.GA9731@stefanha-thinkpad.redhat.com> References: <1375639805-1943-1-git-send-email-alex@alex.org.uk> <1375780592-22842-1-git-send-email-alex@alex.org.uk> <20130806153857.GA9731@stefanha-thinkpad.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] [PATCHv6 00/16] aio / timers: Add AioContext timers and use ppoll List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Kevin Wolf , Anthony Liguori , Alex Bligh , qemu-devel@nongnu.org, liu ping fan , Stefan Hajnoczi , MORITA Kazutaka , rth@twiddle.net > For anyone wishing to review this series, here's a diagram showing the > new relationships and a summary of this series: > > http://vmsplice.net/~stefan/timerlist.jpg > > TimerList is the list of QEMUTimers which are pending on a QEMUClock > clock source. I just started reviewing this and the diagram may be different in v7, anyway: why do you need a default TimerListGroup? I would have thought it is enough to use the default AioContext's own TLG. Paolo > Previously QEMUClock contained this list inline but the goal is to let > AioContexts have their own independent timer lists. This makes timers > much more thread-friendly since we don't work on global lists and > callbacks are dispatched in the same thread's AioContext where they were > created. > > TimerListGroup holds a timerlist for each clock source ("rt", "vm", and > "host"). The main loop has the default TimerListGroup. Each AioContext > has its own TimerListGroup. > > The other major change is that QEMU now uses the event loop's poll() > timeout value instead of a separate OS-specific timer mechanism (aka the > "alarm timer"). > > Stefan >