qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v3 0/3] ppc/spapr: Fix migration of radix guests
Date: Fri, 26 May 2017 15:55:53 +1000	[thread overview]
Message-ID: <20170526055553.GM12929@umbus.fritz.box> (raw)
In-Reply-To: <1495601614-18586-1-git-send-email-bharata@linux.vnet.ibm.com>

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

On Wed, May 24, 2017 at 10:23:31AM +0530, Bharata B Rao wrote:
> This patchset fixes the migration of sPAPR radix guests.

Since Juan has approved merging the latest spin on the
unregister_savevm() patch through my tree, I've merged that, along
with your update 2/3 and 3/3 here.  I did rework 2/3 a bit to remove
unnecessary code motion.

> 
> Changes in v3:
> --------------
> - Dropped the patch that made h_register_process_table flags global as
>   it is not required with the changed logic.
> - The post load logic is now same for both TCG as well as KVM radix guests.
>   Also ensured that radix and future v3 hash migration post load is
>   treated similarly.
> - Ensure TCG Radix guest migration isn't broken.
> 
> v2: https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg04491.html
> 
> Bharata B Rao (3):
>   migration: Introduce unregister_savevm_live()
>   spapr: Unregister HPT savevm handlers for radix guests
>   spapr: Fix migration of Radix guests
> 
>  hw/ppc/spapr.c              | 111 +++++++++++++++++++++++++-------------------
>  include/hw/ppc/spapr.h      |   2 +
>  include/migration/vmstate.h |   1 +
>  migration/savevm.c          |  17 ++++++-
>  4 files changed, 80 insertions(+), 51 deletions(-)
> 

-- 
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 --]

      parent reply	other threads:[~2017-05-26  5:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24  4:53 [Qemu-devel] [PATCH v3 0/3] ppc/spapr: Fix migration of radix guests Bharata B Rao
2017-05-24  4:53 ` [Qemu-devel] [PATCH v3 1/3] migration: Introduce unregister_savevm_live() Bharata B Rao
2017-05-24  6:28   ` Juan Quintela
2017-05-24  6:36     ` David Gibson
2017-05-24  7:18       ` Juan Quintela
2017-05-24  4:53 ` [Qemu-devel] [PATCH v3 2/3] spapr: Unregister HPT savevm handlers for radix guests Bharata B Rao
2017-05-26  4:11   ` Bharata B Rao
2017-05-24  4:53 ` [Qemu-devel] [PATCH v3 3/3] spapr: Fix migration of Radix guests Bharata B Rao
2017-05-24  6:16   ` Suraj Jitindar Singh
2017-05-26  5:55 ` David Gibson [this message]

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=20170526055553.GM12929@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).