All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	Shriram Rajagopalan <rshriram@cs.ubc.ca>,
	Hongyang Yang <yanghy@cn.fujitsu.com>,
	Vijay Kilari <vijay.kilari@gmail.com>
Cc: Xen-devel List <xen-devel@lists.xen.org>
Subject: Migration v2 and related work for 4.6
Date: Wed, 1 Apr 2015 12:03:51 +0100	[thread overview]
Message-ID: <551BD097.2030208@citrix.com> (raw)

Hello,

I believe I have CC'd all interested parties.  If I have missed anyone,
please shout.

There are several large series:
* Cancellable async operations
* COLO

and a wish to start experimenting with migration on ARM which all
interact with my large series for migration v2 support in libxc and libxl.

I am working on the libxl side of things, but realise that I am being a
blockage to the other areas waiting on migration v2.

The current state of the libxc bit is functionally complete.  It is
shipping in two versions of XenServer, has not changed substantially in
9 months, and not changed in a backwards incompatible way since v1.

I propose that the libxc series be accepted independently of the libxl
series.  The libxc series is still implemented as an API-compatible
alternative to legacy migration, and is not enabled by default, meaning
no change to current users.

However, it will unblock development of ARM migration and COLO, and will
allow people in the wider community to experiment with migration v2.  An
existing `xl migrate` can be swapped from legacy to migration v2 simply
by setting an environment variable (for PV guests.  HVM requires the
libxl changed as the handling of the Qemu save record is changing.)

I feel that this is best interest for the community, to get some testing
available earlier in the development cycle, rather than attempting to
splice 3 large series in a related area together towards the code freeze.

Thoughts? (especially from a release management point of view)

~Andrew

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 11:03 Andrew Cooper [this message]
2015-04-02  9:03 ` Migration v2 and related work for 4.6 Ian Campbell
2015-04-02  9:34   ` Andrew Cooper
2015-04-07 12:00     ` Wei Liu
2015-04-07 12:58       ` Andrew Cooper
2015-04-21 10:36       ` Lars Kurth
2015-04-07 11:59 ` Wei Liu
2015-04-15 12:52   ` Ian Campbell
2015-04-15 12:57     ` Andrew Cooper
2015-04-15 13:23       ` 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=551BD097.2030208@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=rshriram@cs.ubc.ca \
    --cc=vijay.kilari@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.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.