All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
	danielhb413@gmail.com, groug@kaod.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: ppc pbr403 vmstate
Date: Tue, 18 Jan 2022 10:11:01 +0100	[thread overview]
Message-ID: <07126f9a-c42e-8b25-9d9e-dff148377f3b@kaod.org> (raw)
In-Reply-To: <CAFEAcA9fcjH7Om8rDMdQ+=cvjaJjWEg2j=CvjE3Lk3kZ0d_y7g@mail.gmail.com>

On 1/17/22 21:40, Peter Maydell wrote:
> On Mon, 17 Jan 2022 at 05:52, David Gibson <david@gibson.dropbear.id.au> wrote:
>> It is also touched in the *super* old cpu_load_old.  I suspect we
>> could probably just drop that completely, since I don't think we
>> realistically support migration from a version that old anyway.
> 
> This would be a nice thing to do, because the PPC CPU is the
> only remaining in-tree user of the .load_state_old migration
> hook, so if we declared that we don't support migrating from
> those old versions of QEMU (1.5 and earlier, I think) then we
> could delete the .load_state_old and .minimum_version_id_old
> handling completely.

yes. It should be fine for PPC.

Thanks,

C.


      reply	other threads:[~2022-01-18  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 18:51 ppc pbr403 vmstate Dr. David Alan Gilbert
2022-01-13 23:41 ` David Gibson
2022-01-14  7:07   ` Cédric Le Goater
2022-01-17  5:52     ` David Gibson
2022-01-17  9:45       ` Cédric Le Goater
2022-01-17  9:52         ` Dr. David Alan Gilbert
2022-01-17 20:40       ` Peter Maydell
2022-01-18  9:11         ` Cédric Le Goater [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=07126f9a-c42e-8b25-9d9e-dff148377f3b@kaod.org \
    --to=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --cc=lvivier@redhat.com \
    --cc=peter.maydell@linaro.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.