From: Jianjun Duan <duanj@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, duanj@linux.vnet.ibm.com, dmitry@daynix.com,
peter.maydell@linaro.org, kraxel@redhat.com, mst@redhat.com,
david@gibson.dropbear.id.au, pbonzini@redhat.com,
veroniabahaa@gmail.com, quintela@redhat.com,
amit.shah@redhat.com, mreitz@redhat.com, kwolf@redhat.com,
rth@twiddle.net, aurelien@aurel32.net, leon.alrae@imgtec.com,
blauwirbel@gmail.com, mark.cave-ayland@ilande.co.uk,
mdroth@linux.vnet.ibm.com
Subject: [Qemu-devel] [QEMU RFC PATCH v4 0/6] migration: ensure hotplug and migration work together
Date: Wed, 8 Jun 2016 16:06:51 -0700 [thread overview]
Message-ID: <1465427217-5551-1-git-send-email-duanj@linux.vnet.ibm.com> (raw)
v4: - Introduce a way to set customized instance_id in SaveStateEntry. Use it
to set instance_id for DRC using its unique index to address David
Gibson's concern.
- Rename VMS_CSTM to VMS_LINKED based on Paolo Bonzini's suggestions.
- Clean up qjson stuff in put_qtailq.
- Add trace for put_qtailq and get_qtailq based on David Gilbert's
suggestion.
It is based on David's ppc-for-2.7. Comments are welcome. Previous versions are:
v3: - Simplify overall design followng discussion with Paolo. No longer need
metadata to migrate QTAILQ.
- Extend VMStateInfo instead of adding similar fields to VMStateField.
- Clean up macros in qemu/queue.h.
(link: https://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg05695.html)
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.
(link: https://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg04188.html)
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.
Jianjun Duan (6):
migration: alternative way to set instance_id in SaveStateEntry
migration: defined VMStateDescription struct for spapr_drc
migration: extend VMStateInfo
migration: migrate QTAILQ
migration: migrate ccs_list in spapr state
migration: migrate pending_events of spapr state
hw/net/vmxnet3.c | 18 +++--
hw/nvram/eeprom93xx.c | 6 +-
hw/nvram/fw_cfg.c | 6 +-
hw/pci/msix.c | 6 +-
hw/pci/pci.c | 12 ++--
hw/pci/shpc.c | 5 +-
hw/ppc/spapr.c | 67 ++++++++++++++++++
hw/ppc/spapr_drc.c | 69 +++++++++++++++++++
hw/ppc/spapr_events.c | 22 +++---
hw/ppc/spapr_pci.c | 22 ++++++
hw/scsi/scsi-bus.c | 6 +-
hw/timer/twl92230.c | 6 +-
hw/usb/redirect.c | 18 +++--
hw/virtio/virtio-pci.c | 6 +-
hw/virtio/virtio.c | 6 +-
include/hw/ppc/spapr.h | 3 +-
include/hw/ppc/spapr_drc.h | 9 +++
include/hw/qdev-core.h | 6 ++
include/migration/vmstate.h | 36 ++++++++--
include/qemu/queue.h | 32 +++++++++
migration/savevm.c | 25 +++++--
migration/vmstate.c | 161 ++++++++++++++++++++++++++++++++++----------
target-alpha/machine.c | 5 +-
target-arm/machine.c | 12 ++--
target-i386/machine.c | 21 ++++--
target-mips/machine.c | 10 +--
target-ppc/machine.c | 10 +--
target-sparc/machine.c | 5 +-
trace-events | 4 ++
29 files changed, 505 insertions(+), 109 deletions(-)
--
1.9.1
next reply other threads:[~2016-06-08 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 23:06 Jianjun Duan [this message]
2016-06-08 23:06 ` [Qemu-devel] [QEMU RFC PATCH v4 1/6] migration: alternative way to set instance_id in SaveStateEntry Jianjun Duan
2016-06-09 4:35 ` David Gibson
2016-06-08 23:06 ` [Qemu-devel] [QEMU RFC PATCH v4 2/6] migration: defined VMStateDescription struct for spapr_drc Jianjun Duan
2016-06-08 23:06 ` [Qemu-devel] [QEMU RFC PATCH v4 3/6] migration: extend VMStateInfo Jianjun Duan
2016-06-08 23:06 ` [Qemu-devel] [QEMU RFC PATCH v4 4/6] migration: migrate QTAILQ Jianjun Duan
2016-06-08 23:06 ` [Qemu-devel] [QEMU RFC PATCH v4 5/6] migration: migrate ccs_list in spapr state Jianjun Duan
2016-06-08 23:06 ` [Qemu-devel] [QEMU RFC PATCH v4 6/6] migration: migrate pending_events of " Jianjun Duan
2016-06-09 17:59 ` [Qemu-devel] [QEMU RFC PATCH v4 0/6] migration: ensure hotplug and migration work together Jianjun Duan
2016-06-10 3:43 ` Amit Shah
-- strict thread matches above, loose matches on Subject: below --
2016-06-10 16:44 Jianjun Duan
2016-06-14 16:03 ` 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=1465427217-5551-1-git-send-email-duanj@linux.vnet.ibm.com \
--to=duanj@linux.vnet.ibm.com \
--cc=amit.shah@redhat.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=dmitry@daynix.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=leon.alrae@imgtec.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=veroniabahaa@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).