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,
Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: [Qemu-devel] [RFC PATCH v1 0/6] ppc/spapr: Fix migration of radix guests
Date: Wed, 17 May 2017 09:19:16 +0530 [thread overview]
Message-ID: <1494992962-6929-1-git-send-email-bharata@linux.vnet.ibm.com> (raw)
This patchset fixes the migration of sPAPR radix guests.
Changes in v1:
--------------
- Added two patches to fix generic savevm unregistration issues.
- HTAB savevm handlers are now registered/unregistered when HTAB
is created/destroyed instead of doing this in CAS call (as in v0).
TODO:
- I have checks in spapr_post_load() to detect and fail the migration
of radix guest to a host that doesn't support radix. However I couldn't
test this as I am hitting some other unrelated migration failure
when testing this path.
- I have tested may scenarios like
- tcg hash->hash, radix->radix, hash->radix and radix->hash reboot
- kvm hash reboot and migration
- kvm radix reboot and migration
However boot->reboot->migration of radix guest doesn't complete
and this seems to be a different issue to be fixed.
v0: https://lists.gnu.org/archive/html/qemu-ppc/2017-05/msg00197.html
Bharata B Rao (6):
migration: Fix unregister_savevm()
migration: Introduce unregister_savevm_live()
spapr: Make h_register_process_table hcall flags global
spapr: Consolidate HPT freeing code into a routine
spapr: Unregister HPT savevm handlers for radix guests
spapr: Fix migration of Radix guests
hw/net/vmxnet3.c | 2 +-
hw/ppc/spapr.c | 43 +++++++++++++++++++++++++++++++++++++------
hw/ppc/spapr_hcall.c | 38 +++++++++++++++++---------------------
hw/s390x/s390-skeys.c | 2 +-
include/hw/ppc/spapr.h | 14 ++++++++++++++
include/migration/vmstate.h | 4 +++-
migration/savevm.c | 16 +++++++++++++---
slirp/slirp.c | 2 +-
8 files changed, 87 insertions(+), 34 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-17 3:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 3:49 Bharata B Rao [this message]
2017-05-17 3:49 ` [Qemu-devel] [RFC PATCH v1 1/6] migration: Fix unregister_savevm() Bharata B Rao
2017-05-17 6:43 ` David Gibson
2017-05-17 10:12 ` Bharata B Rao
2017-05-17 3:49 ` [Qemu-devel] [RFC PATCH v1 2/6] migration: Introduce unregister_savevm_live() Bharata B Rao
2017-05-17 6:45 ` David Gibson
2017-05-17 7:21 ` Bharata B Rao
2017-05-17 3:49 ` [Qemu-devel] [RFC PATCH v1 3/6] spapr: Make h_register_process_table hcall flags global Bharata B Rao
2017-05-17 3:49 ` [Qemu-devel] [RFC PATCH v1 4/6] spapr: Consolidate HPT freeing code into a routine Bharata B Rao
2017-05-17 6:55 ` David Gibson
2017-05-17 3:49 ` [Qemu-devel] [RFC PATCH v1 5/6] spapr: Unregister HPT savevm handlers for radix guests Bharata B Rao
2017-05-17 6:59 ` David Gibson
2017-05-17 7:18 ` Bharata B Rao
2017-05-17 7:23 ` David Gibson
2017-05-17 3:49 ` [Qemu-devel] [RFC PATCH v1 6/6] spapr: Fix migration of Radix guests Bharata B Rao
2017-05-17 7:00 ` David Gibson
2017-05-17 7:15 ` Bharata B Rao
2017-05-17 7:20 ` David Gibson
2017-05-18 5:03 ` Bharata B Rao
2017-05-18 5:50 ` David Gibson
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=1494992962-6929-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 \
/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).