All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "Andrew Jones" <drjones@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Aaron Lindsay" <aaron@os.amperecomputing.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: ARM Snapshots Not Backwards-Compatible
Date: Wed, 3 Feb 2021 10:38:49 +0000	[thread overview]
Message-ID: <CAFEAcA9_mcXHd5m+Z2M1jvk58kGVEcYKF+0kVsLJTjwB9MZcfw@mail.gmail.com> (raw)
In-Reply-To: <20210203102758.GC2950@work-vm>

On Wed, 3 Feb 2021 at 10:28, Dr. David Alan Gilbert <dgilbert@redhat.com> wrote:
>
> * Philippe Mathieu-Daudé (philmd@redhat.com) wrote:
> > Cc'ing migration team and qemu-arm@ list.
>
> I'll have to leave the detail of that to the ARM peole; but from a
> migration point of view I think we do want the 64 bit ARM migrations to
> be stable now.  Please tie incompatible changes to machine types.

That is the intention, but because there's no upstream testing
of migration compat, we never notice if we get it wrong.
What is x86 doing to keep cross-version migration working ?

thanks
-- PMM


  reply	other threads:[~2021-02-03 10:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  4:01 ARM Snapshots Not Backwards-Compatible Aaron Lindsay
2021-02-03  8:21 ` Philippe Mathieu-Daudé
2021-02-03 10:27   ` Dr. David Alan Gilbert
2021-02-03 10:38     ` Peter Maydell [this message]
2021-02-03 10:49       ` Dr. David Alan Gilbert
2021-02-03 10:52         ` Peter Maydell
2021-02-03 10:59           ` Dr. David Alan Gilbert
2021-02-03 16:04             ` Philippe Mathieu-Daudé
2021-02-03 12:44           ` Andrew Jones
2021-02-03 15:45             ` aaron--- via
2021-02-03 15:53               ` Andrew Jones
2021-02-03 10:01 ` Peter Maydell
2021-02-03 14:58   ` Aaron Lindsay
2021-02-03 15:02     ` Philippe Mathieu-Daudé
2021-02-03 15:10       ` Dr. David Alan Gilbert
2021-02-03 15:26         ` Peter Maydell
2021-02-03 15:54           ` Aaron Lindsay
2021-02-03 16:13           ` [PATCH] target/arm: Don't migrate CPUARMState.features Aaron Lindsay
2021-02-03 16:24             ` Philippe Mathieu-Daudé
2021-02-03 20:06             ` Andrew Jones
2021-02-08 13:11             ` Peter Maydell
2021-02-03 15:42         ` ARM Snapshots Not Backwards-Compatible aaron--- via

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=CAFEAcA9_mcXHd5m+Z2M1jvk58kGVEcYKF+0kVsLJTjwB9MZcfw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=aaron@os.amperecomputing.com \
    --cc=dgilbert@redhat.com \
    --cc=drjones@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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.