From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Laurent Vivier <lvivier@redhat.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [Qemu-devel] [PATCH] migration: fix analyze-migration.py script with radix table
Date: Tue, 5 Dec 2017 13:14:56 +0000 [thread overview]
Message-ID: <20171205131455.GC2405@work-vm> (raw)
In-Reply-To: <20171205130420.GM3057@umbus.fritz.box>
* David Gibson (david@gibson.dropbear.id.au) wrote:
> On Tue, Dec 05, 2017 at 12:44:40PM +0000, Dr. David Alan Gilbert wrote:
> > * Laurent Vivier (lvivier@redhat.com) wrote:
> > > Since commit 3a38429748 ("Add a "no HPT" encoding to HTAB migration stream")
> > > the HTAB migration stream contains a header set to "-1", meaning there
> > > is no HPT. Teach analyze-migration.py to ignore the section in this case.
> > >
> > > Without this fix, the script fails with a dump from a POWER9 guest:
> > >
> > > Traceback (most recent call last):
> > > File "./qemu/scripts/analyze-migration.py", line 602, in <module>
> > > dump.read(dump_memory = args.memory)
> > > File "./qemu/scripts/analyze-migration.py", line 539, in read
> > > section.read()
> > > File "./qemu/scripts/analyze-migration.py", line 250, in read
> > > self.file.readvar(n_valid * self.HASH_PTE_SIZE_64)
> > > File "./qemu/scripts/analyze-migration.py", line 64, in readvar
> > > raise Exception("Unexpected end of %s at 0x%x" % (self.filename, self.file.tell()))
> > > Exception: Unexpected end of migrate.dump at 0x1d4763ba
> > >
> > > Fixes: 3a38429748 ("Add a "no HPT" encoding to HTAB migration stream")
> > > Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> >
> > Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> Should I queue this (for 2.12), or do you want to take it via the
> migration tree?
We can take it via migration.
Dave
> >
> > > ---
> > > scripts/analyze-migration.py | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/scripts/analyze-migration.py b/scripts/analyze-migration.py
> > > index 14553876a2..88ff4adb30 100755
> > > --- a/scripts/analyze-migration.py
> > > +++ b/scripts/analyze-migration.py
> > > @@ -234,6 +234,10 @@ class HTABSection(object):
> > >
> > > header = self.file.read32()
> > >
> > > + if (header == -1):
> > > + # "no HPT" encoding
> > > + return
> > > +
> > > if (header > 0):
> > > # First section, just the hash shift
> > > return
>
> --
> 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
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-12-05 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 12:27 [Qemu-devel] [PATCH] migration: fix analyze-migration.py script with radix table Laurent Vivier
2017-12-05 12:44 ` Dr. David Alan Gilbert
2017-12-05 13:04 ` David Gibson
2017-12-05 13:14 ` Dr. David Alan Gilbert [this message]
2017-12-05 19:48 ` Greg Kurz
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=20171205131455.GC2405@work-vm \
--to=dgilbert@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).