From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 2/3] virtio-pci: Use ioeventfd for virtqueue notify
Date: Thu, 11 Nov 2010 18:59:29 +0200 [thread overview]
Message-ID: <4CDC20F1.1030305@redhat.com> (raw)
In-Reply-To: <1289483242-6069-3-git-send-email-stefanha@linux.vnet.ibm.com>
On 11/11/2010 03:47 PM, Stefan Hajnoczi wrote:
> Some virtio devices are known to have guest drivers which expect a notify to be
> processed synchronously and spin waiting for completion. Only enable ioeventfd
> for virtio-blk and virtio-net for now.
Which drivers are these?
I only know of the virtio-gl driver, which isn't upstream.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-11-11 16:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 13:47 [PATCH v2 0/3] virtio: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2010-11-11 13:47 ` [PATCH 1/3] virtio-pci: Rename bugs field to flags Stefan Hajnoczi
2010-11-11 13:47 ` [PATCH 2/3] virtio-pci: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2010-11-11 15:53 ` Michael S. Tsirkin
2010-11-12 9:18 ` Stefan Hajnoczi
2010-11-12 9:25 ` Michael S. Tsirkin
2010-11-12 13:10 ` Stefan Hajnoczi
2010-11-11 16:45 ` Christoph Hellwig
2010-11-12 9:20 ` [Qemu-devel] " Stefan Hajnoczi
2010-11-14 10:34 ` Avi Kivity
2010-11-14 10:37 ` Stefan Hajnoczi
2010-11-14 11:05 ` Avi Kivity
2010-11-14 12:19 ` Avi Kivity
2010-11-15 11:20 ` Stefan Hajnoczi
2010-12-01 11:44 ` Stefan Hajnoczi
2010-12-01 12:30 ` Avi Kivity
2010-12-01 21:34 ` Stefan Hajnoczi
2010-12-06 15:09 ` Avi Kivity
2010-11-11 16:59 ` Avi Kivity [this message]
2010-11-11 17:12 ` Michael S. Tsirkin
2010-11-11 17:55 ` Gleb Natapov
2010-11-11 13:47 ` [PATCH 3/3] virtio-pci: Don't use ioeventfd on old kernels Stefan Hajnoczi
2010-11-11 17:46 ` [PATCH v2 0/3] virtio: Use ioeventfd for virtqueue notify Michael S. Tsirkin
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=4CDC20F1.1030305@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.