All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: Laurent Vivier <lvivier@redhat.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] spapr/ppc: fix backward migration to QEMU 2.9
Date: Wed, 21 Jun 2017 16:05:46 +0800	[thread overview]
Message-ID: <20170621080546.GC12089@umbus> (raw)
In-Reply-To: <20170620161901.50113a5d@bahia.lab.toulouse-stg.fr.ibm.com>

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

On Tue, Jun 20, 2017 at 04:19:01PM +0200, Greg Kurz wrote:
> On Tue, 20 Jun 2017 15:08:47 +0200
> Laurent Vivier <lvivier@redhat.com> wrote:
> 
> > On 19/06/2017 19:05, Greg Kurz wrote:
> > > Commit c783b0012708 ("ppc: Rework CPU compatibility testing across
> > > migration") added a subsection to the vmstate description of CPUs.
> > > This subsection is sent when the CPU compat_pvr field is non-zero,
> > > which is likely to happen after CAS negociation (since QEMU 2.9) or
> > > even before CAS negociation if the user explicitely asked for compat
> > > mode.
> > > 
> > > This breaks backward migration of existing pseries-2.9 machine types
> > > since they don't know about this "compat" subsection:
> > > 
> > > qemu-system-ppc64: error while loading state for instance 0x0 of
> > >  device 'cpu'
> > > 
> > > This patch reverts to the behavior of simply ignoring the PVR when
> > > migrating older machines (ie, let the migration succeed if the user
> > > is sure that the CPU on the destination is close enough to work).
> > > 
> > > Signed-off-by: Greg Kurz <groug@kaod.org>  
> > 
> > Reviewed-by: Laurent Vivier <lvivier@redhat.com>
> > 
> > but I think it should be merged with patch ("ppc: Rework CPU
> > compatibility testing across migration") that is not merged and in the
> > maintainer tree.
> > 
> 
> I agree this would be better for bisect.

As suggested, folded into the existing patch.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

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

      reply	other threads:[~2017-06-21  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 17:05 [Qemu-devel] [PATCH] spapr/ppc: fix backward migration to QEMU 2.9 Greg Kurz
2017-06-20 13:08 ` [Qemu-devel] [Qemu-ppc] " Laurent Vivier
2017-06-20 14:19   ` Greg Kurz
2017-06-21  8:05     ` David Gibson [this message]

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=20170621080546.GC12089@umbus \
    --to=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.