xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>,
	Frediano Ziglio <frediano.ziglio@citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 0/6] [VERY RFC] Migration Stream v2
Date: Wed, 23 Apr 2014 15:02:39 +0100	[thread overview]
Message-ID: <5357C7FF.2090104@citrix.com> (raw)
In-Reply-To: <1398260877.18537.118.camel@kazak.uk.xensource.com>

On 23/04/14 14:47, Ian Campbell wrote:
> On Wed, 2014-04-09 at 19:28 +0100, Andrew Cooper wrote:
>> Hello,
>>
>> Presented here for early review is a basic implementation of PV guest
>> migration using the v2 stream format.
>>
>> PV non-live migration is believed-working; i.e. xl save/restore.
> Based on comments I've seen elsewhere I think the state of the art has
> moved on pretty significantly since this posting. Unless you'd like me
> to I intend skip reviewing this iteration in favour of the next, is that
> OK or would you still like comments on this one?
>
> Ian.
>

Feel free to skip the review of this series if you wish.

The current state of play is that PV migration is completely working.

I am fixing a batching issue. The first version of the code did the
really obvious, dumb, slow actions, for simplicity, and is now being
updated to batch mapping hypercalls for speed.

David is working on HVM migration which is substantially more simple
than PV.

I hope to have another series posted before the end of the week.

~Andrew

  reply	other threads:[~2014-04-23 14:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 18:28 [PATCH 0/6] [VERY RFC] Migration Stream v2 Andrew Cooper
2014-04-09 18:28 ` [PATCH 1/6] [HACK] tools/libxc: save/restore v2 framework Andrew Cooper
2014-04-09 18:28 ` [PATCH 2/6] tools/libxc: Stream specification and some common code Andrew Cooper
2014-04-09 18:28 ` [PATCH 3/6] tools/libxc: Scripts for inspection/valdiation of legacy and new streams Andrew Cooper
2014-04-09 18:28 ` [PATCH 4/6] tools/libxc: x86 pv common code Andrew Cooper
2014-04-09 18:28 ` [PATCH 5/6] tools/libxc: x86 pv save implementation Andrew Cooper
2014-04-09 18:28 ` [PATCH 6/6] tools/libxc: x86 pv restore implementation Andrew Cooper
2014-04-10 10:42 ` [PATCH 0/6] [VERY RFC] Migration Stream v2 Ian Campbell
2014-04-10 11:21   ` Andrew Cooper
2014-04-10 13:05     ` Frediano Ziglio
2014-04-10 13:49       ` Andrew Cooper
2014-04-14 17:49     ` George Dunlap
2014-04-14 18:06       ` Andrew Cooper
2014-04-14 18:16         ` George Dunlap
2014-04-14 23:43           ` Andrew Cooper
2014-04-14 18:11       ` David Vrabel
2014-04-15  8:30         ` Frediano Ziglio
2014-04-15 10:35         ` Ian Jackson
2014-04-15 10:38           ` George Dunlap
2014-04-23 13:47 ` Ian Campbell
2014-04-23 14:02   ` Andrew Cooper [this message]
2014-04-23 14:13     ` 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=5357C7FF.2090104@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.com \
    --cc=frediano.ziglio@citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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).