From: Paolo Bonzini <pbonzini@redhat.com>
To: Felipe Franciosi <felipe@nutanix.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vhost-scsi: Update 'ioeventfd_started' with host notifiers
Date: Mon, 7 Nov 2016 18:32:32 +0100 [thread overview]
Message-ID: <b38e1d7e-a61c-ec63-4865-fa0f23b6920d@redhat.com> (raw)
In-Reply-To: <30DD3181-A1B5-4411-BDC8-2DF176782C20@nutanix.com>
On 07/11/2016 18:26, Felipe Franciosi wrote:
> > @@ -95,6 +95,7 @@ static int vhost_scsi_start(VHostSCSI *s)
> > if (ret < 0) {
> > return ret;
> > }
> > + VIRTIO_BUS(qbus)->ioeventfd_started = true;
>
> I'm not sure if it's safe to do this from
> vhost_dev_disable/enable_notifiers() directly. If you'd rather this
> is fixed there, please let me know and I'll send a v2. This e-mail is
> basically to flag a problem which I recently came across when working
> on vhost-user-scsi. Basically my code stopped working and I didn't
> know why, so I rolled back to test a traditional vhost-scsi on master
> and found this.
>
> I have also not tested vhost-sock, but I imagine it might suffer from
> the same issue (even if it doesn't manifest itself this easily). Any
> other cases you can think of?
Hi Felipe,
can you try overriding start_ioeventfd and stop_ioeventfd (like
ad07cd69ecaffbaa015459a46975ab32e50df805 for regular virtio-scsi), so
that they point to vhost_scsi_start and vhost_scsi_stop? You should not
even need vhost_scsi_set_status anymore.
I'm not sure however why vhost-vsock checks vdev->vm_running, but
otherwise the same should apply to vhost-vsock as well.
Thanks,
Paolo
next prev parent reply other threads:[~2016-11-07 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 17:23 [Qemu-devel] [PATCH] vhost-scsi: Update 'ioeventfd_started' with host notifiers Felipe Franciosi
2016-11-07 17:26 ` Felipe Franciosi
2016-11-07 17:32 ` Paolo Bonzini [this message]
2016-11-08 17:18 ` Paolo Bonzini
2016-11-08 17:23 ` Felipe Franciosi
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=b38e1d7e-a61c-ec63-4865-fa0f23b6920d@redhat.com \
--to=pbonzini@redhat.com \
--cc=felipe@nutanix.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).