From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xensource.com
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
linux-pm@lists.linux-foundation.org,
Iam Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0/3] xen: Use PM/Hibernate events for save/restore/chkpt
Date: Sat, 19 Feb 2011 15:12:35 -0800 [thread overview]
Message-ID: <1298157158-5421-1-git-send-email-rshriram__26444.2028747455$1298158031$gmane$org@cs.ubc.ca> (raw)
The current implementation of xen guest save/restore/checkpoint functionality
uses PM_SUSPEND and PM_RESUME events. This is not optimal when taking
checkpoints of a virtual machine (where the suspend hypercall returns
non-zero, requiring the devices and xenbus to just pickup from where they left
off instead of a complete teardown/reconnect to backend).
The following set of patches modify this implementation to use Hibernate style
control flow (freeze/restore for save/restore and freeze/thaw for checkpoint,
which is merely a cancelled save akin to failed swsusp() ).
These patches are against Ian Campbell's PVHVM tree at
git://xenbits.xen.org/people/ianc/linux-2.6.git for-stefano/pvhvm
at commit 8a8d1bc753c4e2dda5f2890292d60c67d6ebb573
kernel version: 2.6.38-rc4
Save/Restore and Checkpoint functionality have been tested on PV and PV-HVM
Guest Domains. Patches have been run through checkpatch.pl.
Changes since last resend(s):
- xenbus_pm_ops has static const qualifier..
- The conditional macro CONFIG_HIBERNATION around the freeze/thaw/restore
cases in pm_op and pm_noirq_op functions in drivers/base/power/main.c has
been expanded to CONFIG_HIBERNATION || CONFIG_XEN_SAVE_RESTORE.
- CONFIG_PM_SLEEP in drivers/xen/manage.c has been changed to
CONFIG_XEN_SAVE_RESTORE
Kazuhiro SUZUKI (1):
xen: xenbus PM events support
Shriram Rajagopalan (2):
xen: use freeze/restore/thaw PM events for suspend/resume/chkpt
PM: pm.h - Add comments about Xen save/restore/chkpt use case
drivers/base/power/main.c | 8 ++++----
drivers/xen/manage.c | 16 ++++++++--------
drivers/xen/xenbus/xenbus_probe.c | 12 ++++++++++--
drivers/xen/xenbus/xenbus_probe.h | 3 ++-
drivers/xen/xenbus/xenbus_probe_frontend.c | 11 +++++++++--
include/linux/pm.h | 19 +++++++++++++++++++
include/xen/xenbus.h | 2 +-
7 files changed, 53 insertions(+), 18 deletions(-)
next reply other threads:[~2011-02-19 23:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 23:12 Shriram Rajagopalan [this message]
2011-02-19 23:12 [PATCH 0/3] xen: Use PM/Hibernate events for save/restore/chkpt Shriram Rajagopalan
2011-02-20 7:49 ` Pavel Machek
2011-02-20 7:49 ` Pavel Machek
2011-02-21 10:05 ` Ian Campbell
2011-02-21 10:05 ` Ian Campbell
2011-02-21 16:40 ` Alan Stern
2011-02-23 18:38 ` Pavel Machek
2011-02-23 20:10 ` Rafael J. Wysocki
2011-02-23 20:10 ` Rafael J. Wysocki
2011-02-23 18:38 ` Pavel Machek
2011-02-21 16:40 [linux-pm] " Alan Stern
2011-02-21 17:17 ` Ian Campbell
2011-02-21 20:23 ` Rafael J. Wysocki
2011-02-25 16:17 ` Stefano Stabellini
2011-02-25 16:19 ` Ian Campbell
2011-02-25 16:19 ` [linux-pm] " Ian Campbell
2011-02-25 16:23 ` Stefano Stabellini
2011-02-25 16:17 ` Stefano Stabellini
2011-02-21 20:23 ` Rafael J. Wysocki
2011-02-21 17:17 ` Ian Campbell
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='1298157158-5421-1-git-send-email-rshriram__26444.2028747455$1298158031$gmane$org@cs.ubc.ca' \
--to=rshriram@cs.ubc.ca \
--cc=ian.campbell@citrix.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.