From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v2 0/7] migration: s390x css migration
Date: Mon, 29 May 2017 15:55:13 +0200 [thread overview]
Message-ID: <20170529135520.101429-1-pasic@linux.vnet.ibm.com> (raw)
The scope of this patch series is now limited to decoupling channel
subsystem migration from the migration of virtio-ccw proxies.
The vmstatifying of virtio-ccw proxies is now done by another series
currently consisting of a single patch running under the name 'vmstatify
config migration for virtio-ccw'. Since this series depends on that
patch, I have included it here too (for convenience).
The reorganization was requested by Dave.
v1 --> v2:
* Split out the vmystatify virtio-ccw part, reorganize
* Use WITH_TMP instead of one-shot VMStateInfo's
Halil Pasic (7):
s390x: vmstatify config migration for virtio-ccw
s390x: add helper get_machine_class
s390x: add css_migration_enabled to machine class
s390x/css: add missing css state conditionally
s390x/css: add ORB to SubchDev
s390x/css: activate ChannelSubSys migration
s390x/css: use SubchDev.orb
hw/intc/s390_flic.c | 48 ++++
hw/s390x/ccw-device.c | 10 +
hw/s390x/ccw-device.h | 4 +
hw/s390x/css.c | 494 +++++++++++++++++++++++++------------
hw/s390x/s390-virtio-ccw.c | 58 +++--
hw/s390x/virtio-ccw.c | 155 ++++++------
include/hw/s390x/css.h | 17 +-
include/hw/s390x/s390-virtio-ccw.h | 7 +
include/hw/s390x/s390_flic.h | 5 +
9 files changed, 544 insertions(+), 254 deletions(-)
--
2.11.2
next reply other threads:[~2017-05-29 13:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 13:55 Halil Pasic [this message]
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 1/7] s390x: vmstatify config migration for virtio-ccw Halil Pasic
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 2/7] s390x: add helper get_machine_class Halil Pasic
2017-06-01 11:13 ` Cornelia Huck
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 3/7] s390x: add css_migration_enabled to machine class Halil Pasic
2017-06-01 11:16 ` Cornelia Huck
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 4/7] s390x/css: add missing css state conditionally Halil Pasic
2017-05-31 18:52 ` Juan Quintela
2017-06-01 9:35 ` Halil Pasic
2017-06-01 11:32 ` Cornelia Huck
2017-06-01 11:46 ` Halil Pasic
2017-06-07 18:03 ` Juan Quintela
2017-06-08 8:52 ` Halil Pasic
2017-06-01 11:42 ` Cornelia Huck
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 5/7] s390x/css: add ORB to SubchDev Halil Pasic
2017-06-01 11:45 ` Cornelia Huck
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 6/7] s390x/css: activate ChannelSubSys migration Halil Pasic
2017-06-01 8:40 ` Thomas Huth
2017-06-01 10:12 ` Halil Pasic
2017-06-01 11:47 ` Cornelia Huck
2017-05-29 13:55 ` [Qemu-devel] [PATCH v2 7/7] s390x/css: use SubchDev.orb Halil Pasic
2017-06-01 11:50 ` Cornelia Huck
2017-05-31 16:46 ` [Qemu-devel] [PATCH v2 0/7] migration: s390x css migration Dr. David Alan Gilbert
2017-06-01 11:51 ` Cornelia Huck
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=20170529135520.101429-1-pasic@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@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).