From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
sam.bobroff@au1.ibm.com, rnsastry@linux.vnet.ibm.com,
sjitindarsingh@gmail.com
Subject: Re: [Qemu-devel] [PATCH v5 1/2] spapr: Add a "no HPT" encoding to HTAB migration stream
Date: Thu, 8 Jun 2017 16:01:56 +1000 [thread overview]
Message-ID: <20170608060156.GD25805@umbus.fritz.box> (raw)
In-Reply-To: <20170608042848.GA13397@umbus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Thu, Jun 08, 2017 at 02:28:48PM +1000, David Gibson wrote:
> On Wed, Jun 07, 2017 at 01:24:52PM +0530, Bharata B Rao wrote:
> > Add a "no HPT" encoding (using value -1) to the HTAB migration
> > stream (in the place of HPT size) when the guest doesn't allocate HPT.
> > This will help the target side to match target HPT with the source HPT
> > and thus enable successful migration.
> >
> > Suggested-by: David Gibson <david@gibson.dropbear.id.au>
> > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
>
> As dicussed in the thread on the previous version, I still think you
> can use section_hdr == 0 as the no-HPT encoding (matching htab_shift
> == 0.
Bharata discussed this with me on IRC and pointed out I was mistaken.
It thought the overall stream header was distinct from the incremental
content, but it's not. The zero value in the header marks this
"chunk" of data as being continuing incremental content (the "middle"
of the stream) rather than the initial stream header which gives the
HPT size.
So, yes, we do need a new and different encoding for "no HPT".
--
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: 819 bytes --]
next prev parent reply other threads:[~2017-06-08 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 7:54 [Qemu-devel] [PATCH v5 0/2] ppc/spapr: Fix migration of radix guests Bharata B Rao
2017-06-07 7:54 ` [Qemu-devel] [PATCH v5 1/2] spapr: Add a "no HPT" encoding to HTAB migration stream Bharata B Rao
2017-06-08 4:28 ` David Gibson
2017-06-08 6:01 ` David Gibson [this message]
2017-06-07 7:54 ` [Qemu-devel] [PATCH v5 2/2] spapr: Fix migration of Radix guests Bharata B Rao
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=20170608060156.GD25805@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rnsastry@linux.vnet.ibm.com \
--cc=sam.bobroff@au1.ibm.com \
--cc=sjitindarsingh@gmail.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).