From: Jaeyong Yoo <jaeyong.yoo@samsung.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH RFC 2/4] Implement arch_hvm_save and arch_hvm_load functions
Date: Wed, 05 Jun 2013 10:46:51 +0000 (GMT) [thread overview]
Message-ID: <24280375.35201370429210845.JavaMail.weblogic@epv6ml01> (raw)
> > I think if we use all of them for safety check, it is sufficient.
> >
> > (Maybe it is too much?)
>
> Perhaps we should leave this to one side for now and revisit once we
> have a working save/restore and understand the constraints upon it a bit
> better?
Sure, of course.
Jaeyong
next reply other threads:[~2013-06-05 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 10:46 Jaeyong Yoo [this message]
[not found] <85.CD.07473.B821FA15@epcpsbgx2.samsung.com>
2013-06-05 10:40 ` [PATCH RFC 2/4] Implement arch_hvm_save and arch_hvm_load functions Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 10:27 Jaeyong Yoo
2013-06-05 5:46 [PATCH RFC 0/4] arm: regarding live migration 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
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=24280375.35201370429210845.JavaMail.weblogic@epv6ml01 \
--to=jaeyong.yoo@samsung.com \
--cc=Ian.Campbell@citrix.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).