From: Jianjun Duan <duanj@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, mdroth@linux.vnet.ibm.com,
david@gibson.dropbear.id.au, amit.shah@redhat.com,
quintela@redhat.com, duanj@linux.vnet.ibm.com
Subject: [Qemu-devel] [QEMU RFC PATCH v2 0/6] Migration: ensure hotplug and migration work together
Date: Tue, 24 May 2016 10:55:03 -0700 [thread overview]
Message-ID: <1464112509-21806-1-git-send-email-duanj@linux.vnet.ibm.com> (raw)
v2: - Introduce a general approach to migrate QTAILQ in qemu/queue.h.
- Migrate signalled field in the DRC state.
- Put the newly added migrating fields in subsections so that backward migration is not broken.
- Set detach_cb field right after migration so that a migrated hot-unplug event could finish its course.
v1: - Inital version.
(link: https://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02601.html)
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.
Alexey Kardashevskiy (1):
vmstate: Define VARRAY with VMS_ALLOC
Jianjun Duan (5):
spapr: ensure device trees are always associated with DRC
Migration: Defined VMStateDescription struct for spapr_drc
Migration: migrate QTAILQ
Migration: migrate ccs_list in spapr state
Migration: migrate pending_events of spapr state
hw/ppc/spapr.c | 92 ++++++++++++++++++++++++++++++++++++++++-----
hw/ppc/spapr_drc.c | 61 ++++++++++++++++++++++++++++++
hw/ppc/spapr_events.c | 22 ++++++-----
hw/ppc/spapr_pci.c | 34 +++++++++++++----
include/hw/ppc/spapr.h | 3 +-
include/hw/ppc/spapr_drc.h | 9 +++++
include/migration/vmstate.h | 69 ++++++++++++++++++++++++++++++++++
include/qemu/queue.h | 38 +++++++++++++++++++
migration/vmstate.c | 84 +++++++++++++++++++++++++++++++++++++++++
9 files changed, 385 insertions(+), 27 deletions(-)
--
1.9.1
next reply other threads:[~2016-05-24 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 17:55 Jianjun Duan [this message]
2016-05-24 17:55 ` [Qemu-devel] [QEMU RFC PATCH v2 1/6] spapr: ensure device trees are always associated with DRC Jianjun Duan
2016-05-25 5:20 ` David Gibson
2016-05-24 17:55 ` [Qemu-devel] [QEMU RFC PATCH v2 2/6] Migration: Defined VMStateDescription struct for spapr_drc Jianjun Duan
2016-05-24 17:55 ` [Qemu-devel] [QEMU RFC PATCH v2 3/6] vmstate: Define VARRAY with VMS_ALLOC Jianjun Duan
2016-05-24 17:55 ` [Qemu-devel] [QEMU RFC PATCH v2 4/6] Migration: migrate QTAILQ Jianjun Duan
2016-05-25 5:38 ` David Gibson
2016-05-25 8:14 ` Paolo Bonzini
2016-05-25 16:37 ` Jianjun Duan
2016-05-25 17:51 ` Paolo Bonzini
2016-05-25 18:30 ` Jianjun Duan
2016-05-25 19:22 ` Paolo Bonzini
2016-05-25 20:17 ` Jianjun Duan
2016-05-26 7:11 ` Paolo Bonzini
2016-05-26 16:43 ` Jianjun Duan
2016-05-26 16:52 ` Paolo Bonzini
2016-05-24 17:55 ` [Qemu-devel] [QEMU RFC PATCH v2 5/6] Migration: migrate ccs_list in spapr state Jianjun Duan
2016-05-24 17:55 ` [Qemu-devel] [QEMU RFC PATCH v2 6/6] Migration: migrate pending_events of " Jianjun Duan
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=1464112509-21806-1-git-send-email-duanj@linux.vnet.ibm.com \
--to=duanj@linux.vnet.ibm.com \
--cc=amit.shah@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.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).