From: Yonit Halperin <yhalperi@redhat.com>
To: qemu-devel@nongnu.org
Cc: Yonit Halperin <yhalperi@redhat.com>,
aliguori@us.ibm.com, alevy@redhat.com, kraxel@redhat.com
Subject: [Qemu-devel] [RFC PATCH 0/5] asynchronous migration state change handlers
Date: Tue, 5 Jun 2012 08:49:41 +0300 [thread overview]
Message-ID: <1338875386-21051-1-git-send-email-yhalperi@redhat.com> (raw)
Hi,
I'm sending this patch series again. This time with an additional patch
for setting a migrate_end notifier completion callback for spice migration
interface. I've also added more detailed commit messages.
This patch series introduces async handlers for notifiers, and integrates them
with migration state change notifications.
Asynchronous migration completion notifier is essential for allowing spice to cleanly
complete the src server connection to the client, and transfer the connection to the target.
Currently, as soon as the migration completes, the src qemu can be closed by the
management, and spice cannot complete the spice-connection migration.
In order to support spice seamless migration, next to these patches, I plan to add:
(1) notifier for switching from the live phase of the migration to the non-live phase,
before completing savevm.
Spice will use this notification to "finalize" the connection to the client: send
and receive all in-flight data.
(2) add vmstates for spice data that need to be migrated, e.g., usb/agent/smartcard
buffers that were sent from the client and haven't been written to device yet.
We would also want to migrate data that will allow us to continue the new spice
connection from the same point the old one stopped. Without requiring special
treatment in the client side.
Regards,
Yonit.
Yonit Halperin (5):
notifiers: add support for async notifiers handlers
migration: moving migration start code to a separated routine
migration: moving migration completion code to a separated routine
migration: replace migration state change notifier with async
notifiers
spice: turn spice "migration end" handler to be async
input.c | 2 +-
migration.c | 154 ++++++++++++++++++++++++++++++++++++++++---------------
migration.h | 11 +++-
notify.c | 78 ++++++++++++++++++++++++++--
notify.h | 55 ++++++++++++++++++--
qemu-timer.c | 2 +-
ui/spice-core.c | 58 +++++++++++++++------
vl.c | 2 +-
8 files changed, 290 insertions(+), 72 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-06-05 5:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 5:49 Yonit Halperin [this message]
2012-06-05 5:49 ` [Qemu-devel] [RFC PATCH 1/5] notifiers: add support for async notifiers handlers Yonit Halperin
2012-06-05 8:36 ` Gerd Hoffmann
2012-06-05 5:49 ` [Qemu-devel] [RFC PATCH 2/5] migration: moving migration start code to a separated routine Yonit Halperin
2012-06-05 8:44 ` Gerd Hoffmann
2012-06-05 5:49 ` [Qemu-devel] [RFC PATCH 3/5] migration: moving migration completion " Yonit Halperin
2012-06-05 8:46 ` Gerd Hoffmann
2012-06-05 5:49 ` [Qemu-devel] [RFC PATCH 4/5] migration: replace migration state change notifier with async notifiers Yonit Halperin
2012-06-05 5:49 ` [Qemu-devel] [RFC PATCH 5/5] spice: turn spice "migration end" handler to be async Yonit Halperin
2012-06-05 11:59 ` [Qemu-devel] [RFC PATCH 0/5] asynchronous migration state change handlers Anthony Liguori
2012-06-05 13:15 ` Gerd Hoffmann
2012-06-05 13:38 ` Eric Blake
2012-06-05 21:37 ` Anthony Liguori
2012-06-06 9:10 ` Yonit Halperin
2012-06-06 9:22 ` Anthony Liguori
2012-06-06 10:54 ` Alon Levy
2012-06-06 11:05 ` Anthony Liguori
2012-06-06 11:27 ` Alon Levy
2012-06-06 11:49 ` Anthony Liguori
2012-06-06 12:01 ` Yonit Halperin
2012-06-06 12:08 ` Anthony Liguori
2012-06-06 12:15 ` Alon Levy
2012-06-06 12:17 ` Anthony Liguori
2012-06-06 12:30 ` Alon Levy
2012-06-06 12:34 ` Anthony Liguori
2012-06-06 13:03 ` Gerd Hoffmann
2012-06-06 14:52 ` Alon Levy
2012-06-06 15:00 ` Gerd Hoffmann
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=1338875386-21051-1-git-send-email-yhalperi@redhat.com \
--to=yhalperi@redhat.com \
--cc=alevy@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@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).