From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: xen-devel@lists.xensource.com
Cc: samuel.thibault@ens-lyon.org, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: [PATCH 0/4] stubdom-dm: Support live migration of HVM domain with stubdom-dm
Date: Tue, 16 Dec 2008 18:22:20 +0900 [thread overview]
Message-ID: <4947734C.5070509@ab.jp.nec.com> (raw)
Hi,
This series of patches is an attempt to support live migration of hvm
domains with stubdom-dm.
For hvm domains to live-migrate, we should create a log-dirty shared
memory segment between xc_save and qemu-dm. for a normal qemu-dm,
memory sharing is done by inter process communication interface
(shmget/shmat/shmctl), but it obviously doesn't work for a stubdom-dm
because it is not a dom0 process but a domain itself.
The idea here is to allocate log-dirty the shared memory segment in
the stubdom-dm and to map the memory region into the xc_save process
by using grant table interface.
[PATCH 1/4] mini-os: Make utility function get_self_id() public
[PATCH 2/4] Log-dirty shared memory between stubdom-dm and xc_save
[PATCH 3/4] Log-dirty shared memory between stubdom-dm and xc_save
(ioemu-remote part)
[PATCH 4/4] xend: Give stubdom flag to xc_save
Thanks,
-----------------------
Yosuke Iwamatsu
NEC Corporation
next reply other threads:[~2008-12-16 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 9:22 Yosuke Iwamatsu [this message]
2008-12-16 10:02 ` [PATCH 0/4] stubdom-dm: Support live migration of HVM domain with stubdom-dm Samuel Thibault
2008-12-16 10:06 ` Samuel Thibault
2008-12-16 14:04 ` Ian Jackson
2008-12-16 14:16 ` Samuel Thibault
2008-12-17 1:06 ` Yosuke Iwamatsu
2008-12-17 1:28 ` Samuel Thibault
2008-12-17 11:39 ` Ian Jackson
2008-12-17 13:14 ` Samuel Thibault
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=4947734C.5070509@ab.jp.nec.com \
--to=y-iwamatsu@ab.jp.nec.com \
--cc=keir.fraser@eu.citrix.com \
--cc=samuel.thibault@ens-lyon.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.