From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:59641)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1UFKmP-0007Zy-IV
	for qemu-devel@nongnu.org; Tue, 12 Mar 2013 04:41:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1UFKmN-0005Kq-A2
	for qemu-devel@nongnu.org; Tue, 12 Mar 2013 04:41:53 -0400
Received: from mx1.redhat.com ([209.132.183.28]:10105)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1UFKmN-0005Kh-1K
	for qemu-devel@nongnu.org; Tue, 12 Mar 2013 04:41:51 -0400
Message-ID: <513EEA47.6060303@redhat.com>
Date: Tue, 12 Mar 2013 09:41:43 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1362316883-7948-1-git-send-email-qemulist@gmail.com>
	<20130305213046.GI21850@vm>
	<CAJnKYQmyVLi2FnfvevKG5551PjHKqCMxntvje3jByEjC3P_RWg@mail.gmail.com>
In-Reply-To: <CAJnKYQmyVLi2FnfvevKG5551PjHKqCMxntvje3jByEjC3P_RWg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 0/3] *** make netlayer re-entrant ***
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: liu ping fan <qemulist@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, "Michael S. Tsirkin" <mst@redhat.com>, mdroth <mdroth@linux.vnet.ibm.com>, Anthony Liguori <anthony@codemonkey.ws>, qemu-devel@nongnu.org

Il 07/03/2013 03:06, liu ping fan ha scritto:
> > From what I gathered from the other thread, the path forward was to
> > replace the global iohandler list that we currently use to drive
> > NetClient events and replace it with a GSource and GMainContext, rather
> > than relying on AioContexts.
> 
> Not quite sure about it. Seems that AioContext is built on GSource, so
> I think they are similar, and AioContext is easy to reuse.

AioContext is designed so that it can be used either independently (as
virtio-blk-dataplane does now) or as a GSource (as we do for the "main"
AioContext, which is used for the block layer and where qemu_bh_new
places bottom halves).

Paolo