From: rshriram@cs.ubc.ca
To: xen-devel@lists.xensource.com
Cc: brendan@cs.ubc.ca, ian.jackson@eu.citrix.com, ian.campbell@citrix.com
Subject: [PATCH 0 of 2 V2] libxl - Remus support
Date: Tue, 31 Jan 2012 20:44:11 -0800 [thread overview]
Message-ID: <patchbomb.1328071451@athos.nss.cs.ubc.ca> (raw)
This patch series introduces a basic framework to
incorporate Remus into the libxl toolstack. The only functionality
currently implemented is memory checkpointing.
These patches depend on Version 2 of
"libxl: refactor suspend/resume code" patch series.
Changes since previous version:
* Move libxl_domain_remus_start into the save_callbacks implementation patch
* return proper error codes instead of -1.
* Add documentation to docs/man/xl.pod.1
Shriram
next reply other threads:[~2012-02-01 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 4:44 rshriram [this message]
2012-02-01 4:44 ` [PATCH 1 of 2 V2] libxl: Remus - suspend/postflush/commit callbacks rshriram
2012-02-01 4:44 ` [PATCH 2 of 2 V2] libxl: Remus - xl remus command rshriram
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.1328071451@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=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 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).