From: rshriram@cs.ubc.ca
To: xen-devel@lists.xensource.com
Cc: brendan@cs.ubc.ca, stefano.stabellini@eu.citrix.com,
ian.campbell@citrix.com, ian.jackson@citrix.com
Subject: [PATCH 0 of 2 V4] libxl - Remus support
Date: Thu, 09 Feb 2012 17:58:00 -0800 [thread overview]
Message-ID: <patchbomb.1328839080@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
1. "V3 libxl: refactor suspend/resume code" patch series (patches 1,2,3,5,6)
(note: patches 1 & 2 have already been committed and others have been
acked by Ian Campbell)
2. V4 of "libxl: support suspend_cancel in domain_resume"
(message id: 47366457a52076b78c52.1328837508@athos.nss.cs.ubc.ca)
3. Stefano's "V4 libxl: save/restore qemu physmap"
Changes in V4:
* more explanation on blackhole replication in xl.pod
* moved comment on save_callbacks to xenguest.h
* rebased to current tip, removed useless comments.
Changes in V3:
* Rebased w.r.t Stefano's patches.
Changes in V2:
* 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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2012-02-10 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 1:58 rshriram [this message]
2012-02-10 1:58 ` [PATCH 1 of 2 V4] libxl: Remus - suspend/postflush/commit callbacks rshriram
2012-02-10 1:58 ` [PATCH 2 of 2 V4] libxl: Remus - xl remus command rshriram
2012-02-20 19:04 ` [PATCH 0 of 2 V4] libxl - Remus support Ian Jackson
2012-02-20 20:06 ` 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.1328839080@athos.nss.cs.ubc.ca \
--to=rshriram@cs.ubc.ca \
--cc=brendan@cs.ubc.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=stefano.stabellini@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 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.