From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xen.org
Cc: brendan@cs.ubc.ca, ian.jackson@eu.citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: [PATCH 0 of 4 RESEND V6] libxl: refactor suspend/resume code
Date: Thu, 22 Mar 2012 12:48:24 -0700 [thread overview]
Message-ID: <patchbomb.1332445704@athos.nss.cs.ubc.ca> (raw)
This patch series refactors the suspend/resume code in libxl to minimize
Remus specific code in libxl. There are a couple of trivial bug fixes too.
Changes in V6:
Rebase patches to the latest tip.
Depends on Stefano's "V6: libxl: save/restore qemu physmap".
Changes in V5:
Rebase patches to the latest tip.
Depends on Stefano's "V5: libxl: save/restore qemu physmap".
Changes in V4:
1. Incorporated Ian Campbell's comments on the suspend_cancel support patch.
Changes in V3:
1. rebase patches based on Stefano's patches
use qmp_save instead of qmp_migrate
2. check if qemu moves to "running" state after resuming the device model
3. Moved comments on the co-operative suspend to libxl.h
Changes in V2:
1. migrate code is refactored as save_config , create child,
do_preamble instead of coaelscing them all into one single
function.
2. More documentation for suspend_cancel parameter in domain_resume
3. Minor nits
Shriram
next reply other threads:[~2012-03-22 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 19:48 Shriram Rajagopalan [this message]
2012-03-22 19:48 ` [PATCH 1 of 4 RESEND V6] libxl: QMP stop/resume & refactor QEMU suspend/resume/save Shriram Rajagopalan
2012-03-22 19:48 ` [PATCH 2 of 4 RESEND V6] libxl: support suspend_cancel in domain_resume Shriram Rajagopalan
2012-03-22 19:48 ` [PATCH 3 of 4 RESEND V6] libxl: refactor migrate_domain and generalize migrate_receive Shriram Rajagopalan
2012-03-22 19:48 ` [PATCH 4 of 4 RESEND V6] libxl: resume instead of unpause on xl save -c Shriram Rajagopalan
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=patchbomb.1332445704@athos.nss.cs.ubc.ca \
--to=rshriram@cs.ubc.ca \
--cc=brendan@cs.ubc.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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).