All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Vijay Kilari <vijay.kilari@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VM Migration on ARM
Date: Wed, 11 Mar 2015 11:47:58 +0000	[thread overview]
Message-ID: <1426074478.21353.200.camel@citrix.com> (raw)
In-Reply-To: <55002144.7020007@linaro.org>

On Wed, 2015-03-11 at 11:04 +0000, Julien Grall wrote:
> Hi,
> 
> On 11/03/2015 10:51, Andrew Cooper wrote:
> > On 11/03/15 05:32, Vijay Kilari wrote:
> >> Hi Andrew,
> >>
> >>      From Ian & Stefano, I came to know that you have introduced
> >> Migration framework v2
> >> under below patch series
> >>
> >> http://marc.info/?l=xen-devel&m=141036915311145
> >>
> >> I have few queries:
> >>
> >> 1) Is there any plans/timeline to support for ARM32/ARM64?.
> >
> > I will not personally be doing any ARM migration support, not even as
> > part of getting migration v2 accepted upstream.

Just to be clear, I don't expect you to do anything of the sort either,
other than keeping ARM as is compiling of course.

> FWIW, there is a patch series on the ML for supporting migration v1 [1].
> But the author doesn't work on it anymore, so AFAIK nobody touched it 
> since this version.

Right.

Some parts of that series could still be a useful starting point, and
for the rest I expect that the (re)implementation on top of Andrew's
work should be almost trivial.

IMO it ought to be reasonably easy to get save/restore and
dead-migration working based on the combination of those two series, and
I think this should be done first before move on to looking at all the
log-dirty stuff and p2m frobbing which is needed to perform a live
migration, which is going to be far more time consuming to get right.

Ian.

  reply	other threads:[~2015-03-11 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  5:32 VM Migration on ARM Vijay Kilari
2015-03-11 10:51 ` Andrew Cooper
2015-03-11 11:04   ` Julien Grall
2015-03-11 11:47     ` Ian Campbell [this message]
2015-03-20 12:17   ` Vijay Kilari
2015-03-25 16:02     ` Andrew Cooper
2015-03-27 13:32       ` Vijay Kilari
2015-03-27 13:47         ` Andrew Cooper

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=1426074478.21353.200.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=vijay.kilari@gmail.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 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.