From: Wei Huang <w1.huang@samsung.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: stefano.stabellini@eu.citrix.com, yjhyun.yoo@samsung.com,
ian.campbell@citrix.com, jaeyong.yoo@samsung.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH 0/6] xen/arm: Xen save/restore/live migration support
Date: Fri, 11 Apr 2014 10:36:23 -0500 [thread overview]
Message-ID: <53480BF7.4020007@samsung.com> (raw)
In-Reply-To: <5347FD36.1060608@linaro.org>
On 04/11/2014 09:33 AM, Julien Grall wrote:
> On 04/11/2014 03:22 PM, Wei Huang wrote:
>> On 04/11/2014 09:15 AM, Julien Grall wrote:
>>> Hi Wei,
>>>
>>> Thank you for the series, I plan to give a try on midway. On which board
>>> did you try the migration?
>> I tested the patches on a system with A15 CPUs. I don't see any problem
>> to run them on midway. You need patches for DomU to support migration.
>> Most of them were from Jaeyong's patch posted before (I made some
>> modification). IMO they are hack-ish, so I didn't post them here. I can
>> set them to you in private email. Let me know.
>
> Is it the one posted in July 2013? If you have an updated version, can
> you send me the series?
Yes, it was from July 2013.
>
>>>
>>> On 04/10/2014 05:48 PM, Wei Huang wrote:
>>>> The following are the save/restore/live-migration patches I
>>>> forward-ported to
>>>> the latest Xen tree. Note that I kept the order of original patches, and
>>>> Signed-off-by as well. For the patches I modified (see summary below), I
>>>> added my name as Signed-off-by.
>>>>
>>>> These patches aren't intended as the final version. Since Junghyun
>>>> Yoo is
>>>> working on his patches, I think it is better to send out my version now
>>>> for discussion and proper merge. Let us make Xen 4.5 support these
>>>> features.
>>>>
>>>> === Modification Summary ===
>>>>
>>>> Patch 1:
>>>> * Adapt to latest Xen source code
>>>> * Setting IRQ status as enabled by checking ieanble bits after
>>>> loading VM info
>>>> * Minor fixes to support 64-bit
>>>>
>>>> Patch 5:
>>>> * Add new p2m ARM type (p2m_ram_logdirty) to support dirty page tracking
>>>>
>>>> Patch 6:
>>>> * Enable save/restore/live migration support based on latest Xen code
>>>> * Adapt to latest Xen source code
>>>
>>> Might be a stupid, did you go through the different comments on the v5
>>> sent by Jaeyong? Sorry if it was the case.
>> Not completely. I will work on them in next revision. If Junghyun has
>> fixes, please post them too.
>
> Thanks, I will wait the next version before reviewing. I don't want to
> bother you with the same comments :).
>
> Regards,
>
next prev parent reply other threads:[~2014-04-11 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 16:48 [PATCH 0/6] xen/arm: Xen save/restore/live migration support Wei Huang
2014-04-10 16:48 ` [PATCH 1/6] xen/arm: Save and restore support for hvm context hypercall Wei Huang
2014-04-10 17:26 ` Andrew Cooper
2014-04-10 21:53 ` Wei Huang
2014-04-11 13:57 ` Julien Grall
2014-04-10 16:48 ` [PATCH 2/6] xen/arm: implement get_maximum_gpfn hypercall Wei Huang
2014-04-10 17:28 ` Andrew Cooper
2014-04-10 21:54 ` Wei Huang
2014-04-11 13:17 ` Julien Grall
2014-04-11 13:15 ` Julien Grall
2014-04-10 16:48 ` [PATCH 3/6] xen/arm: Implement do_suspend function Wei Huang
2014-04-11 14:10 ` Julien Grall
2014-04-10 16:48 ` [PATCH 4/6] xen/arm: Implement VLPT for guest p2m mapping in live migration Wei Huang
2014-04-10 16:48 ` [PATCH 5/6] xen/arm: Implement hypercall for dirty page tracing Wei Huang
2014-04-10 16:48 ` [PATCH 6/6] xen/arm: Implement toolstack for xl restore/save and migrate Wei Huang
2014-04-11 14:15 ` [PATCH 0/6] xen/arm: Xen save/restore/live migration support Julien Grall
2014-04-11 14:22 ` Wei Huang
2014-04-11 14:33 ` Julien Grall
2014-04-11 15:36 ` Wei Huang [this message]
2014-04-11 15:53 ` Julien Grall
2014-04-11 16:15 ` Wei Huang
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=53480BF7.4020007@samsung.com \
--to=w1.huang@samsung.com \
--cc=ian.campbell@citrix.com \
--cc=jaeyong.yoo@samsung.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yjhyun.yoo@samsung.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.