qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	avocado-devel <avocado-devel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	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>
Subject: Re: ARM Snapshots Not Backwards-Compatible
Date: Wed, 3 Feb 2021 17:04:43 +0100	[thread overview]
Message-ID: <d31bcfff-04e3-95e3-a98a-ebe9394366d9@redhat.com> (raw)
In-Reply-To: <20210203105933.GF2950@work-vm>

On 2/3/21 11:59 AM, Dr. David Alan Gilbert wrote:
> * Peter Maydell (peter.maydell@linaro.org) wrote:
>> On Wed, 3 Feb 2021 at 10:49, Dr. David Alan Gilbert <dgilbert@redhat.com> wrote:
>>>
>>> * Peter Maydell (peter.maydell@linaro.org) wrote:
>>>> 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 ?
>>>
>>> I know there used to be some of our team running Avocado tests for
>>> compatibility regularly, I'm not sure of the current status.
>>> It's something we also do regularly around when we do downstream
>>> releases, so we tend to catch them then, although even on x86 that
>>> often turns out to be a bit late.
>>
>> So downstream testing only?
> 
> I thought there used to be some regular avocado testing of upstream but
> I'm not sure if it's all architectures and I'm not sure if it's still
> happening; I haven't seen any migration issues from it for a while,
> which makes me think it isn't.
> 
>> I think that unless we either (a) start
>> doing migration-compat testing consistently upstream or (b) RedHat or
>> some other downstream start testing and reporting compat issues
>> to us for aarch64 as they do for x86-64, in practice we're just
>> not going to have working migration compat despite our best
>> intentions. (None of the issues Aaron raises were deliberate
>> compat breaks -- they're all "we made a change we didn't think
>> affected migration but it turns out that it does".)
> 
> I'd agree; we still hit this too often on x86 as well.

Cc'ing avocado-devel, since previously discussed:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg654139.html



  reply	other threads:[~2021-02-03 16:07 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
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é [this message]
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=d31bcfff-04e3-95e3-a98a-ebe9394366d9@redhat.com \
    --to=philmd@redhat.com \
    --cc=aaron@os.amperecomputing.com \
    --cc=avocado-devel@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=drjones@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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).