From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Wen Congyang <wency@cn.fujitsu.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen-devel List <xen-devel@lists.xen.org>,
Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Hongyang Yang <yanghy@cn.fujitsu.com>,
Vijay Kilari <vijay.kilari@gmail.com>
Subject: Re: Migration v2 and related work for 4.6
Date: Tue, 21 Apr 2015 11:36:42 +0100 [thread overview]
Message-ID: <DB68AD26-EC25-4C69-A4BC-7DA8576FD76E@gmail.com> (raw)
In-Reply-To: <20150407120021.GD14251@zion.uk.xensource.com>
We could discuss at the Hackathon next week, and reply to this thread. It seems that at least 50% of all the stake-holders are in fact there
Regards
Lars
> On 7 Apr 2015, at 13:00, Wei Liu <wei.liu2@citrix.com> wrote:
>
> On Thu, Apr 02, 2015 at 10:34:34AM +0100, Andrew Cooper wrote:
>> On 02/04/15 10:03, Ian Campbell wrote:
>>> On Wed, 2015-04-01 at 12:03 +0100, Andrew Cooper wrote:
>>>> I propose that the libxc series be accepted independently of the libxl
>>>> series.
>>> That is most likely a good idea IMHO.
>>>
>>> What do you estimate the chances of the libxl bit being done for 4.6 to
>>> be?
>>
>> I hope to have everything complete for 4.6, including removal of the
>> legacy code.
>>
>
> Not sure what "legacy code" you're referring to, but we definitely want
> to support 4.5 -> 4.6 migration so the "legacy code" might need to stay
> for 4.6?
>
> Wei.
>
>> Given the current timescales, I would say most likely.
>>
>>>
>>> Is there an option of actually switching to the new libxc without
>>> switching libxl and fixing libxl later, or would that be as much work as
>>> just fixing libxl?
>>
>> For PV guests, yes. One can transparently swap the legacy algorithm
>> from the v2 algorithm and every works.
>>
>> For HVM guests, no. The handling of the Qemu save record and toolstack
>> records needs fixing.
>>
>> In the upgrade case, libxl also needs to take care of piping the legacy
>> stream through the conversion script.
>>
>> ~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-04-21 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 11:03 Migration v2 and related work for 4.6 Andrew Cooper
2015-04-02 9:03 ` 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 [this message]
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=DB68AD26-EC25-4C69-A4BC-7DA8576FD76E@gmail.com \
--to=lars.kurth.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@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.