From: David Gibson <david@gibson.dropbear.id.au>
To: Jianjun Duan <duanj@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 0/5] migration: ensure hotplug and migration work together
Date: Wed, 20 Apr 2016 14:29:57 +1000 [thread overview]
Message-ID: <20160420042957.GD1133@voom> (raw)
In-Reply-To: <1460752385-13259-1-git-send-email-duanj@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Fri, Apr 15, 2016 at 01:33:00PM -0700, Jianjun Duan wrote:
> To make guest device (PCI, CPU and memory) hotplug work together
> with guest migration, spapr drc state needs be transmitted in
> migration. This patch defines the VMStateDescription struct for
> spapr drc state to enable it.
>
> To fix the potential racing between hotplug events on guest and
> guest migration, ccs_list and pending_events of spapr state need be
> transmitted in migration. This patch also takes care of it.
> Especially, temporary cache is used for each of them to enable the
> transmission.
Hmm, so this will certainly have to be for 2.7 at this stage. I have
some concerns that I'll comment on in the individual patches.
--
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 --]
prev parent reply other threads:[~2016-04-20 5:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 20:33 [Qemu-devel] [PATCH 0/5] migration: ensure hotplug and migration work together Jianjun Duan
2016-04-15 20:33 ` [Qemu-devel] [PATCH 1/5] spapr: ensure device trees are always associated with DRC Jianjun Duan
2016-04-20 4:30 ` David Gibson
2016-04-21 16:53 ` [Qemu-devel] [Qemu-ppc] " Jianjun Duan
2016-04-15 20:33 ` [Qemu-devel] [PATCH 2/5] Migration: Defined VMStateDescription struct for spapr_drc Jianjun Duan
2016-04-20 4:32 ` David Gibson
2016-04-21 17:03 ` Jianjun Duan
2016-04-22 4:25 ` David Gibson
2016-04-22 16:47 ` [Qemu-devel] [Qemu-ppc] " Jianjun Duan
2016-04-15 20:33 ` [Qemu-devel] [PATCH 3/5] vmstate: Define VARRAY with VMS_ALLOC Jianjun Duan
2016-04-15 20:33 ` [Qemu-devel] [PATCH 4/5] Migration: migrate ccs_list in spapr state Jianjun Duan
2016-04-20 5:14 ` David Gibson
2016-04-21 17:22 ` Jianjun Duan
2016-04-22 4:28 ` David Gibson
2016-04-22 16:55 ` Jianjun Duan
2016-04-15 20:33 ` [Qemu-devel] [PATCH 5/5] Migration: migrate pending_events of " Jianjun Duan
2016-04-20 4:29 ` 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=20160420042957.GD1133@voom \
--to=david@gibson.dropbear.id.au \
--cc=duanj@linux.vnet.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).