From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au,
sam.bobroff@au1.ibm.com, rnsastry@linux.vnet.ibm.com,
sjitindarsingh@gmail.com,
Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v4 0/2] ppc/spapr: Fix migration of radix guests
Date: Wed, 31 May 2017 16:56:43 +0530 [thread overview]
Message-ID: <1496230005-12265-1-git-send-email-bharata@linux.vnet.ibm.com> (raw)
This patchset fixes the migration of sPAPR radix guests.
Changes in v4
-------------
- The earlier approach of keeping the HTAB savevm handlers registered
only for hash guests by explicitly deregistering does leave out a few
corner cases which become ugly/difficult to fix. Hence based on
David Gibson's suggestion, this new approach adds a new
"no HPT" encoding into the migration stream when guest doesn't
allocate HPT.
- There are a few assumptions in HTAB savevm handlers that spapr->htab
will not be set only for KVM guests. This is no longer true with
radix TCG guests. Fix this assumption. These changes enable TCG migration
to work. However guest kernel failures are observed post migration which
need to be fixed separately. This changes could acutally go into
a separate patch.
v3: https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg05434.html
Bharata B Rao (2):
spapr: Add a "no HPT" encoding to HTAB migration stream
spapr: Fix migration of Radix guests
hw/ppc/spapr.c | 43 +++++++++++++++++++++++++++++--------------
1 file changed, 29 insertions(+), 14 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-31 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 11:26 Bharata B Rao [this message]
2017-05-31 11:26 ` [Qemu-devel] [PATCH v4 1/2] spapr: Add a "no HPT" encoding to HTAB migration stream Bharata B Rao
2017-06-01 4:54 ` David Gibson
2017-06-07 7:53 ` Bharata B Rao
2017-06-08 4:21 ` David Gibson
2017-05-31 11:26 ` [Qemu-devel] [PATCH v4 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=1496230005-12265-1-git-send-email-bharata@linux.vnet.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--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).