qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Dave Airlie <airlied@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] dataplane, thread and gpu stuff
Date: Tue, 19 Nov 2013 15:20:12 +0100	[thread overview]
Message-ID: <20131119142012.GB3202@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <528A4240.7040409@redhat.com>

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

      reply	other threads:[~2013-11-19 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18  4:52 [Qemu-devel] dataplane, thread and gpu stuff Dave Airlie
2013-11-18 15:03 ` Stefan Hajnoczi
2013-11-18 16:18   ` Anthony Liguori
2013-11-19 14:20     ` Stefan Hajnoczi
2013-11-18 16:37   ` Paolo Bonzini
2013-11-19 14:20     ` Stefan Hajnoczi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131119142012.GB3202@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=airlied@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).