qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: 'Christian Borntraeger' <borntraeger@de.ibm.com>,
	Pavel Fedin <p.fedin@samsung.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vhost: Fix aborting if KVM does not support eventfds
Date: Wed, 25 Nov 2015 17:10:29 +0800	[thread overview]
Message-ID: <20151125091029.GD7357@stefanha-x1.localdomain> (raw)
In-Reply-To: <20151118231639-mutt-send-email-mst@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]

On Wed, Nov 18, 2015 at 11:25:32PM +0200, Michael S. Tsirkin wrote:
> On Tue, Nov 17, 2015 at 10:17:37AM +0300, Pavel Fedin wrote:
> > If you happen to have a stock kernel of old version, like 3.x,
> 
> On ARM
> 
> > and you
> > attempt to enable vhost by setting vhost=on, qemu aborts with error:
> > kvm_mem_ioeventfd_add: error adding ioeventfd: Function not implemented
> > 
> > This patch adds capability check, so that vhost gets disabled instead. A
> > warning is displayed, explaining the reason:
> > 
> > 2015-11-13T08:43:51.146802Z qemu-system-aarch64: KVM does not support eventfd binding
> > 2015-11-13T08:43:51.146915Z qemu-system-aarch64: unable to start vhost net: 38: falling back on userspace virtio
> > 
> > This problem can be observed with libvirt, which checks for /dev/vhost-net
> > availability and just inserts "vhost=on" automatically in this case.
> > 
> > Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
> > ---
> > v1 => v2:
> > - Removed "MMIO" from warning message, because it applies not only to MMIO
> > - Add note about warning to the commit message
> > ---
> >  hw/virtio/vhost.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
> > index 1794f0d..50b8171 100644
> > --- a/hw/virtio/vhost.c
> > +++ b/hw/virtio/vhost.c
> > @@ -24,6 +24,7 @@
> >  #include "hw/virtio/virtio-bus.h"
> >  #include "hw/virtio/virtio-access.h"
> >  #include "migration/migration.h"
> > +#include "sysemu/kvm.h"
> >  
> >  static struct vhost_log *vhost_log;
> >  static struct vhost_log *vhost_log_shm;
> > @@ -1083,6 +1084,11 @@ int vhost_dev_enable_notifiers(struct vhost_dev *hdev, VirtIODevice *vdev)
> >          r = -ENOSYS;
> >          goto fail;
> >      }
> > +    if (!kvm_eventfds_enabled()) {
> > +        error_report("KVM does not support eventfd binding");
> > +        r = -ENOSYS;
> > +        goto fail;
> > +    }
> >  
> >      for (i = 0; i < hdev->nvqs; ++i) {
> >          r = k->set_host_notifier(qbus->parent, hdev->vq_index + i, true);
> 
> That's a wrong thing for vhost to do - we don't want it
> poking at kvm because it does not work with either kvm or
> eventfd.  It uses host notifiers, there should be an
> API to check for that.
> 
> Or better yet, actually implement host notifiers
> in userspace - should not be that hard to do, just
> do write into eventfd.

I sent this RFC patch a while back:
https://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg04710.html

My intent was to write a qtest for a vhost device but I didn't complete
the work.  Anyway, this patch might be useful.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-11-25  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  7:17 [Qemu-devel] [PATCH v2] vhost: Fix aborting if KVM does not support eventfds Pavel Fedin
2015-11-18 21:25 ` Michael S. Tsirkin
2015-11-25  9:10   ` Stefan Hajnoczi [this message]
2015-11-25 10:13     ` Pavel Fedin

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=20151125091029.GD7357@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=borntraeger@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=p.fedin@samsung.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).