From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49562)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VimAC-0005I2-Vq
	for qemu-devel@nongnu.org; Tue, 19 Nov 2013 09:20:33 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VimA4-0005Zk-E4
	for qemu-devel@nongnu.org; Tue, 19 Nov 2013 09:20:24 -0500
Received: from mail-we0-x235.google.com ([2a00:1450:400c:c03::235]:42200)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VimA4-0005ZW-7X
	for qemu-devel@nongnu.org; Tue, 19 Nov 2013 09:20:16 -0500
Received: by mail-we0-f181.google.com with SMTP id x55so3986618wes.26
	for <qemu-devel@nongnu.org>; Tue, 19 Nov 2013 06:20:15 -0800 (PST)
Date: Tue, 19 Nov 2013 15:20:12 +0100
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20131119142012.GB3202@stefanha-thinkpad.redhat.com>
References: <CAPM=9tybWan07M47APA3UPxXrmJc0AUH1mFUbUNoSmYmVZvk3w@mail.gmail.com>
	<20131118150340.GA4083@stefanha-thinkpad.redhat.com>
	<528A4240.7040409@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <528A4240.7040409@redhat.com>
Subject: Re: [Qemu-devel] dataplane, thread and gpu stuff
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: Dave Airlie <airlied@gmail.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Mon, Nov 18, 2013 at 05:37:20PM +0100, Paolo Bonzini wrote:
> Il 18/11/2013 16:03, Stefan Hajnoczi ha scritto:
> > As of today, there are still two vring implementations in
> > hw/virtio/virtio.c and hw/virtio/dataplane/vring.c.  This means it isn't
> > clean and easy to integrate into a new device yet.  Existing dataplane
> > devices basically take advantage of the fact that the non-dataplane
> > version sets up the device before I/O.
> > 
> > Paolo can give you details on the latest thread-safe memory API stuff
> > and whether it's already usable for virtio.
> 
> vring and virtio are still separate even in my latest patches.  I have
> patches to convert vring to use memory_region_find instead of hostmem.
> 
> > Regarding irqfd, we could emulate it in TCG using an EventNotifier
> > (eventfd).  At that point I think it's no longer kvm-specific.
> 
> I think he's talking about ioeventfd though.

ioeventfd can be emulated using EventNotifier too, although it depends
on the handler function whether or not it's worth deferring it to
another thread.

Stefan