qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
	qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] virtio-net: mark VIRTIO_NET_F_GSO as legacy
Date: Mon, 7 Nov 2016 20:43:26 +0100	[thread overview]
Message-ID: <c06c1198-9848-9c15-0054-99b960be56cb@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161107153853.GF2054@work-vm>



On 11/07/2016 04:38 PM, Dr. David Alan Gilbert wrote:
> * Michael S. Tsirkin (mst@redhat.com) wrote:
>> > virtio 1.0 spec says this is a legacy feature bit,
>> > hide it from guests in legacy mode.
>> > 
>> > Note: for cross-version migration compatibility,
>> > we keep the bit set in host_features.
>> > The result will be that a guest migrating cross-version
>> > will see host features change under it.
>> > As guests only seem to read it once, this should
>> > not be an issue. Meanwhile, will work to fix guests to
>> > ignore this bit in virtio1 mode, too.
> OK, but if they're actually using the feature they'll carry
> on working ?
> 
> Dave
> 

The interesting scenario is when we migrate form older to newer
(otherwise the bugous situation can't emerge in the first place). Now
the change affects only what the guest sees when it reads host_features,
and that should happen only during the feature negotiation (once). That
means the change won't have any observable effect unless a reset
happens. And if we have a reset, then things are going to work out
correctly avoiding the bugous (but still working) state in both host and
guest. So yes, both will happily carry on using the feature, and carry
on working.

Halil

  reply	other threads:[~2016-11-07 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 11:01 [Qemu-devel] [PATCH 0/2] virtio-net: spec compatibility fix Michael S. Tsirkin
2016-11-04 11:01 ` [Qemu-devel] [PATCH 1/2] virtio: allow per-device-class legacy features Michael S. Tsirkin
2016-11-04 11:32   ` Cornelia Huck
2016-11-07  9:11   ` Jason Wang
2016-11-04 11:01 ` [Qemu-devel] [PATCH 2/2] virtio-net: mark VIRTIO_NET_F_GSO as legacy Michael S. Tsirkin
2016-11-04 11:37   ` Cornelia Huck
2016-11-07  9:11   ` Jason Wang
2016-11-07 15:38   ` Dr. David Alan Gilbert
2016-11-07 19:43     ` Halil Pasic [this message]
2016-11-07 19:25   ` Halil Pasic

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=c06c1198-9848-9c15-0054-99b960be56cb@linux.vnet.ibm.com \
    --to=pasic@linux.vnet.ibm.com \
    --cc=dgilbert@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).