From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: kwolf@redhat.com,
"Denis Plotnikov" <den-plotnikov@yandex-team.ru>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
raphael.norwitz@nutanix.com,
"Roman Kagan" <rvkagan@yandex-team.ru>,
yc-core@yandex-team.ru, pbonzini@redhat.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v0 0/2] virtio-blk and vhost-user-blk cross-device migration
Date: Wed, 6 Oct 2021 04:36:10 -0400 [thread overview]
Message-ID: <20211006043314-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <YV1eQmM/+HXZy06C@work-vm>
On Wed, Oct 06, 2021 at 09:28:50AM +0100, Dr. David Alan Gilbert wrote:
> To me it feels the same as the distinction between vhost-kernel and qemu
> backended virtio that we get in net and others - in principal it's just
> another implementation.
In net it's actually like this. Same -device, a different netdev.
> A tricky part is guaranteeing the set of visible virtio features between
> implementations; we have that problem when we use vhost-kernel and run
> on a newer/older kernel and gain virtio features; the same will be true
> with vhost-user implementations.
That's not new but yes we need to work on this.
> But this would make the structure of a vhost-user implementation quite
> different.
>
> Dave
Right. That's why I'm reluctant to just add a new device type that
has special compatibility requirements.
> >
> > > > --
> > > > MST
> > > >
> > > --
> > > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-10-06 8:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 15:07 [PATCH v0 0/2] virtio-blk and vhost-user-blk cross-device migration Denis Plotnikov
2021-10-04 15:07 ` [PATCH v0 1/2] vhost-user-blk: add a new vhost-user-virtio-blk type Denis Plotnikov
2021-10-04 15:16 ` Michael S. Tsirkin
2021-10-04 15:07 ` [PATCH v0 2/2] vhost-user-blk-pci: add new pci device type to support vhost-user-virtio-blk Denis Plotnikov
2021-10-04 15:11 ` [PATCH v0 0/2] virtio-blk and vhost-user-blk cross-device migration Michael S. Tsirkin
2021-10-04 23:18 ` Roman Kagan
2021-10-05 6:51 ` Michael S. Tsirkin
2021-10-05 14:01 ` Dr. David Alan Gilbert
2021-10-05 16:10 ` Eduardo Habkost
2021-10-05 22:06 ` Michael S. Tsirkin
2021-10-06 8:09 ` Dr. David Alan Gilbert
2021-10-06 8:17 ` Michael S. Tsirkin
2021-10-06 8:28 ` Dr. David Alan Gilbert
2021-10-06 8:36 ` Michael S. Tsirkin [this message]
2021-10-06 8:43 ` Dr. David Alan Gilbert
2021-10-06 12:18 ` Michael S. Tsirkin
2021-10-06 13:29 ` Dr. David Alan Gilbert
2021-10-06 13:39 ` Michael S. Tsirkin
2021-10-06 14:27 ` Dr. David Alan Gilbert
2021-10-06 14:37 ` 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=20211006043314-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=den-plotnikov@yandex-team.ru \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=rvkagan@yandex-team.ru \
--cc=yc-core@yandex-team.ru \
/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).