From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: "\"柳澤佳里(yanagisawa yoshisato)\""
<yanagisawa.yoshisato@lab.ntt.co.jp>,
"Ian Pratt" <ian.pratt@citrix.com>,
ian.jackson@eu.citrix.com,
"Keir Fraser" <keir.fraser@eu.citrix.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Subject: [RFC][PATCH 00/13] Kemari: updated to the 3.4 unstable tree
Date: Thu, 12 Mar 2009 10:14:48 +0900 [thread overview]
Message-ID: <49B86208.2020205@lab.ntt.co.jp> (raw)
Hi,
This patch series are updated version of Kemari that we posted last week.
http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00371.html
Thanks for the comments, and we're working to improve and clean up the code
appropriately. The following patches can be applied to the 3.4 unstable tree.
xen, xend: xen-unstable.hg c/s 19303:b249f3e979a5
linux: linux-2.6.18-xen.hg c/s 817:0430b1dbfb3a
ioemu: qemu-xen-unstable.git c/s 82787c6f689d869ad349df83ec3f58702afe00fe
If you can take a look, it would be very helpful.
Any comments are appreciated.
Thanks,
Yoshi
Overview:
Kemari in VMM taps event channel, pauses the guest (not suspend), prepares for
transfer, and Kemari in userland transfers the guest. On failover, Kemari on
the secondary restores the guest, and the backend drivers in dom0 set up the
backend rings from the state of the shared rings in the guest.
[01] xen: add ECS_TAP state to event channel
[02] xen: core Kemari code
[03] xend: change parameter type of xc_{set,get}_hvm_param
[04] xend: Kemari controller interface in libxc
[05] xend: Kemari sender in libxc
[06] xend: Kemari receiver libxc
[07] xend: add Kemari support to python
[08] xend: add dev state "Attached" to python
[09] linux: add XenbusStateAttached to xenbus
[10] linux: XenbusStateAttached handler for blkback
[11] linux: XenbusStateAttached handler for netback
[12] ioemu: use signal to save qemu state for Kemari
[13] ioemu: use shared region with to flip logdirty_bitmap
next reply other threads:[~2009-03-12 1:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 1:14 Yoshiaki Tamura [this message]
2009-03-12 1:15 ` [RFC][PATCH 01/13] Kemari: add ECS_TAP state to event channel Yoshiaki Tamura
2009-03-12 1:16 ` [RFC][PATCH 02/13] Kemari: core kemari code Yoshiaki Tamura
2009-03-12 1:16 ` [RFC][PATCH 03/13] Kemari: change parameter type of xc_{set, get}_hvm_param Yoshiaki Tamura
2009-03-12 1:17 ` [RFC][PATCH 04/13] Kemari: Kemari controller interface in libxc Yoshiaki Tamura
2009-03-12 1:17 ` [RFC][PATCH 05/13] Kemari: Kemari sender Yoshiaki Tamura
2009-03-24 6:59 ` Yoshiaki Tamura
2009-03-12 1:18 ` [RFC][PATCH 06/13] Kemari: Kemari receiver Yoshiaki Tamura
2009-03-12 1:19 ` [RFC][PATCH 07/13] Kemari: add Kemari support to python Yoshiaki Tamura
2009-03-12 1:19 ` [RFC][PATCH 08/13] Kemari: add dev state "Attached" " Yoshiaki Tamura
2009-03-12 1:20 ` [RFC][PATCH 09/13] Kemari: add XenbusStateAttached to xenbus Yoshiaki Tamura
2009-03-12 1:23 ` [RFC][PATCH 13/13] Kemari: use shared region with to flip logdirty_bitmap Yoshiaki Tamura
2009-03-24 6:59 ` Yoshiaki Tamura
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=49B86208.2020205@lab.ntt.co.jp \
--to=tamura.yoshiaki@lab.ntt.co.jp \
--cc=ian.jackson@eu.citrix.com \
--cc=ian.pratt@citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yanagisawa.yoshisato@lab.ntt.co.jp \
/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.