From: Jaeyong Yoo <jaeyong.yoo@samsung.com>
To: xen-devel@lists.xen.org
Cc: Jaeyong Yoo <jaeyong.yoo@samsung.com>
Subject: [PATCH RFC 0/4] arm: regarding live migration
Date: Wed, 05 Jun 2013 14:46:15 +0900 [thread overview]
Message-ID: <1370411179-13570-1-git-send-email-jaeyong.yoo@samsung.com> (raw)
Hi all,
I'm interested in developing live migration in xen arm and possibly
the contribution to the community and I hope this patch series could be a start.
For this matter, I have following questions:
(1) Is it OK to keep using the keyword "hvm"? Or, is it better to use pvh?
(2) After some overview of source code, I think the required parts
for save/restore are the following:
- xen-store info
- shared info page
- memory contents (no need for p2m table)
- cpu/vcpu
- gic/vgic
- drivers
I think there are still important parts that I'm missing.
I appreciate if you could give some advice :)
(3) Regarding split drivers, come to think of it, we have to store
both side (front/back) states, in-flight event channels, IRQs, etc.
And those look like quite a work (although evtchn is migrated within vcpu)
I appreciate if you guys could share any hints from the experience of
migrating split drivers in x86.
Lastly I would like to note that the following patch series is just the
concept work for reviewing my idea and they are quite preliminary.
Jaeyong Yoo (4):
Create new directory for stroing hvm-related files in ARM.
Implement arch_hvm_save and arch_hvm_load functions
Implement save and restore for gic (template impl)
Implement XEN_DOMCTL_gethvmcontext part of arch_do_domctl
xen/arch/arm/Makefile | 2 +-
xen/arch/arm/domctl.c | 58 +++++++++++++++-
xen/arch/arm/hvm.c | 67 ------------------
xen/arch/arm/hvm/Makefile | 2 +
xen/arch/arm/hvm/hvm.c | 118 ++++++++++++++++++++++++++++++++
xen/arch/arm/hvm/save.c | 69 +++++++++++++++++++
xen/common/Makefile | 2 +
xen/include/asm-arm/hvm/support.h | 29 ++++++++
xen/include/public/arch-arm/hvm/save.h | 36 ++++++++++
9 files changed, 314 insertions(+), 69 deletions(-)
delete mode 100644 xen/arch/arm/hvm.c
create mode 100644 xen/arch/arm/hvm/Makefile
create mode 100644 xen/arch/arm/hvm/hvm.c
create mode 100644 xen/arch/arm/hvm/save.c
create mode 100644 xen/include/asm-arm/hvm/support.h
--
1.7.9.5
next reply other threads:[~2013-06-05 5:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 5:46 Jaeyong Yoo [this message]
2013-06-05 5:46 ` [PATCH RFC 1/4] Create new directory for stroing hvm-related files in ARM Jaeyong Yoo
2013-06-05 5:46 ` [PATCH RFC 2/4] Implement arch_hvm_save and arch_hvm_load functions Jaeyong Yoo
2013-06-05 9:17 ` Ian Campbell
2013-06-05 5:46 ` [PATCH RFC 3/4] Implement save and restore for gic (template impl) Jaeyong Yoo
2013-06-05 9:21 ` Ian Campbell
2013-06-05 5:46 ` [PATCH RFC 4/4] Implement XEN_DOMCTL_gethvmcontext part of arch_do_domctl Jaeyong Yoo
2013-06-05 9:24 ` Ian Campbell
2013-06-05 9:13 ` [PATCH RFC 0/4] arm: regarding live migration Ian Campbell
2013-06-05 9:23 ` Ian Campbell
2013-06-05 9:26 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 10:30 Jaeyong Yoo
2013-06-13 1:15 Jaeyong Yoo
2013-06-13 8:21 ` 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=1370411179-13570-1-git-send-email-jaeyong.yoo@samsung.com \
--to=jaeyong.yoo@samsung.com \
--cc=xen-devel@lists.xen.org \
/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).