Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, Jason Wang <jasowang@redhat.com>
Subject: [virtio-dev] Re: Packed ring only devices clarification
Date: Fri, 29 Jan 2021 10:58:23 -0500	[thread overview]
Message-ID: <20210129105653-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <875d1495-9511-4b5d-062c-2063ee9bed7e@redhat.com>

On Fri, Jan 29, 2021 at 09:38:25AM +0100, Maxime Coquelin wrote:
> Hello,
> 
> In the Virtqueues section of the Virtio specification [0], it is
> mentioned that:
> 
> "
> Every driver and device supports either the Packed or the Split
> Virtqueue format, or both.
> "
> 
> However, it seems there is no way to differentiate whether the device
> supports both split and packed ring, or only packed ring by reading
> its features bits.
> 
> In the case of live-migration, it means we would need to trigger a
> features negotiation before the migration is initiated, and see if
> FEATURES_OK device status bit is set. Still, we could not be sure a
> failure would be due to the device supporting only packed ring.
> 
> Is my understanding correct?


The simple answer is that live migration is transparent to
guests and so isn't ATM described by the virtio spec.

devices implementing live migration need not constrain
themselves to using the feature bits described in the spec,
e.g. vhost-user has its own "protocol features".

> If so, maybe we would need to introduce a new feature bit for split
> ring, and also a feature bit indicating compliance with the new spec
> version for backward compatibility:
> 
> VIRTIO_F_VERSION_1_2(39):
>     This indicates compliance with Virtio version 1.2 specification.
> 
> VIRTIO_F_RING_SPLIT(40):
>     This feature indicates support for the split virtqueue layout as
>     described in 2.6 Split Virtqueues.
> 
> 
> Best regards,
> Maxime
> 
> [0]:
> https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html#x1-230005


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2021-01-29 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  8:38 [virtio-dev] Packed ring only devices clarification Maxime Coquelin
2021-01-29  9:04 ` Jason Wang
2021-01-29  9:14   ` Maxime Coquelin
2021-02-01  7:02     ` Jason Wang
2021-01-29 15:58 ` Michael S. Tsirkin [this message]
2021-02-01  7:04   ` [virtio-dev] " Jason Wang

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=20210129105653-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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