From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Felipe Franciosi <felipe@nutanix.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 18/33] vhost-user-scsi: Introduce vhost-user-scsi host device
Date: Wed, 7 Jun 2017 14:56:57 -0400 (EDT) [thread overview]
Message-ID: <1191656469.6862786.1496861817272.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170607212825-mutt-send-email-mst@kernel.org>
> > This could be documented,
>
> It is documented AFAIK. Pls take a look at the spec documentation.
Found it now. It's not under GET_VRING_BASE, it's under "starting
and stopping rings"---fair enough.
In the case of vhost-user-scsi, however, QEMU also must not proceed
until vhost-user-scsi has drained the pending I/O---and this pending
I/O would be completed _after_ QEMU has sent GET_VRING_BASE.
Is this handled by VHOST_USER_PROTOCOL_F_REPLY_ACK already? If so,
migration would be denied if the server lacks that protocol feature.
Paolo
> > but perhaps it's best to add a START_STOP
> > feature and message to the vhost-user protocol?
>
> We just never need to GET_VRING_BASE if ring keeps going -
> makes no sense since base gets invalidated immediately.
>
>
>
> > The feature then can be optional for vhost-user-net and mandatory for
> > vhost-user-scsi. When this is done we can remove .unmigratable.
> >
> > Thanks,
> >
> > Paolo
>
> If vhost-user-scsi does not stop the ring after responding to
> GET_VRING_BASE, it's just a bug that needs to be fixed.
>
> > > >
> > > > Can you please send a version of your patch that uses .unmigratable?
> > >
> > > Sure I can do that. We can work on the migration later on.
> > >
> > > >
> > > > I'll send a v6 that momentarily drops vhost-scsi, but I intend to
> > > > include it again in the next pull request.
> > >
> > > Sounds good to me.
> > >
> > > Felipe
> > >
> > > >
> > > > Thanks,
> > > >
> > > > Paolo
> > >
> > >
>
next prev parent reply other threads:[~2017-06-07 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 15:28 [Qemu-devel] [PULL v5 00/33] Misc patches for 2017-06-01 Paolo Bonzini
2017-06-07 15:28 ` [Qemu-devel] [PULL 18/33] vhost-user-scsi: Introduce vhost-user-scsi host device Paolo Bonzini
2017-06-07 15:37 ` Peter Maydell
2017-06-07 15:39 ` Felipe Franciosi
2017-06-07 15:47 ` Peter Maydell
2017-06-07 18:26 ` Felipe Franciosi
2017-06-07 16:21 ` Paolo Bonzini
2017-06-07 16:26 ` Felipe Franciosi
2017-06-07 18:22 ` Paolo Bonzini
2017-06-07 18:30 ` Michael S. Tsirkin
2017-06-07 18:56 ` Paolo Bonzini [this message]
2017-06-08 0:31 ` Michael S. Tsirkin
2017-06-08 11:05 ` Felipe Franciosi
2017-06-08 13:33 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2017-06-07 13:55 [Qemu-devel] [PULL v4 00/33] Misc patches for 2017-06-01 Paolo Bonzini
2017-06-07 13:55 ` [Qemu-devel] [PULL 18/33] vhost-user-scsi: Introduce vhost-user-scsi host device Paolo Bonzini
2017-06-06 14:02 [Qemu-devel] [PULL v3 00/33] Misc patches for 2017-06-01 Paolo Bonzini
2017-06-06 14:02 ` [Qemu-devel] [PULL 18/33] vhost-user-scsi: Introduce vhost-user-scsi host device Paolo Bonzini
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=1191656469.6862786.1496861817272.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=felipe@nutanix.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).