qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: lvivier@redhat.com, peter.maydell@linaro.org,
	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: Mon, 17 Jan 2022 16:52:07 +1100	[thread overview]
Message-ID: <YeUEB0lb7mhuoP6G@yekko.fritz.box> (raw)
In-Reply-To: <a2b11256-5afe-42de-ffb3-dad07c8165b3@kaod.org>

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

On Fri, Jan 14, 2022 at 08:07:21AM +0100, Cédric le Goater wrote:
> On 1/14/22 00:41, David Gibson wrote:
> > On Thu, Jan 13, 2022 at 06:51:56PM +0000, Dr. David Alan Gilbert wrote:
> > > Hi,
> > >    Is there any easy way of getting a machine where the pbr403 vmstate
> > > would be generated?
> > 
> > The condition in pbr403_needed is...
> > 
> >      return (pvr & 0xffff0000) == 0x00200000;
> > 
> > .. which looks to be the PVR for ppc403 models.  That makes sense with
> > the section name... but not so much with the fact that it's under
> > cpu/tlb6xx.  The 6xx MMU is basically unrelated to the 40x MMU.  But
> > it looks like the vmstate_tlbemb might be shared between then, because
> > of bad ideas of the past.
> > 
> > But in any case, we already dropped what little 403 support we ever
> > had - there's nothing with that PVR even listed in
> > target/ppc/cpu-models.h.
> > 
> > So I think we should just drop it.
> 
> yes. But we can not remove env.pb since this would break migration
> compatibility, correct ?

Only if it appears in a migration section that's actually emitted by a
supported machine type.  As far as I can tell the only section that
does that is vmstate_pbr403, which we're also dropping so we should be
fine.

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.  But
even if we don't want to do that right now, we can just replace the
reads into env->pb with discarding reads and we'll be fine.  We don't
implement any cpus that actually used those fields, so we can ignore
them in the migration stream.

-- 
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: 833 bytes --]

  reply	other threads:[~2022-01-17  5:56 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 [this message]
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

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=YeUEB0lb7mhuoP6G@yekko.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --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 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).