qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org, mst@redhat.com,
	marcel@redhat.com,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] virtio-pci: Fix cross-version migration with older machines
Date: Thu, 15 Dec 2016 10:31:45 +0000	[thread overview]
Message-ID: <20161215103145.GG2762@stefanha-x1.localdomain> (raw)
In-Reply-To: <20161215092656.2e1244c0.cornelia.huck@de.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2683 bytes --]

On Thu, Dec 15, 2016 at 09:26:56AM +0100, Cornelia Huck wrote:
> On Thu, 15 Dec 2016 07:38:09 +0000
> Stefan Hajnoczi <stefanha@gmail.com> wrote:
> 
> > On Wed, Dec 14, 2016 at 05:30:35PM +0100, Maxime Coquelin wrote:
> > > This patch fixes a cross-version migration regression introduced
> > > by commit d1b4259f ("virtio-bus: Plug devices after features are
> > > negotiated").
> > > 
> > > The problem is encountered when host's vhost backend does not support
> > > VIRTIO_F_VERSION_1, and migration is initiated from a v2.7 or prior
> > > machine with virtio-pci modern capabilities enabled to a v2.8 machine.
> > > 
> > > In this case, modern capabilities get exposed to the guest by the source,
> > > whereas the target will detect version 1 is not supported so will only
> > > expose legacy capabilities.
> > > 
> > > The problem is fixed by introducing a new "x-ignore-backend-features"
> > > property, which is set in v2.7 and prior compatibility modes. Doing this,
> > > v2.7 machine keeps its broken behaviour (enabling modern while version
> > > is not supported), and newer machines will behave correctly.
> > > 
> > > Reported-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> > > Suggested-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > Cc: Michael S. Tsirkin <mst@redhat.com>
> > > Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
> > > Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > > Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
> > > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > Tested-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> > > Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> > > ---
> > > 
> > > V3 fixes commit message with the new property name.
> > > V2 changes the naming as proposed by Michael T.and Cornelia, and
> > > fixes commit message.
> > > 
> > >  hw/virtio/virtio-pci.c | 5 ++++-
> > >  hw/virtio/virtio-pci.h | 1 +
> > >  include/hw/compat.h    | 4 ++++
> > >  3 files changed, 9 insertions(+), 1 deletion(-)
> > 
> > Thanks, applied to my staging tree:
> > https://github.com/stefanha/qemu/commits/staging
> > 
> > Stefan
> 
> Hm, missing my R-b I gave for v2... feel free to add
> 
> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> 
> if you still want to change it.

Sorry, the R-b didn't make it into v2.8.0-rc4.

The patch management scripts I use apply all R-b for a single email
thread.  They do not look at previous revisions (it would be hard to
tell which R-b still stand and which do not).  The usual solution is for
the patch author to include previous R-b in new revisions as long as
code changes aren't substantial.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2016-12-15 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 16:30 [Qemu-devel] [PATCH v3] virtio-pci: Fix cross-version migration with older machines Maxime Coquelin
2016-12-14 17:18 ` Stefan Hajnoczi
2016-12-14 22:04 ` Michael S. Tsirkin
2016-12-15  7:38 ` Stefan Hajnoczi
2016-12-15  8:26   ` Cornelia Huck
2016-12-15 10:31     ` Stefan Hajnoczi [this message]
2016-12-15 11:03       ` Maxime Coquelin

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=20161215103145.GG2762@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dgilbert@redhat.com \
    --cc=marcel@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).