From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Migration v2 and related work for 4.6 Date: Tue, 7 Apr 2015 13:58:34 +0100 Message-ID: <5523D47A.7000500@citrix.com> References: <551BD097.2030208@citrix.com> <1427965418.4037.6.camel@citrix.com> <551D0D2A.6030506@citrix.com> <20150407120021.GD14251@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150407120021.GD14251@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Ian Campbell , Wen Congyang , Ian Jackson , Xen-devel List , Shriram Rajagopalan , Hongyang Yang , Vijay Kilari List-Id: xen-devel@lists.xenproject.org On 07/04/15 13:00, Wei Liu 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? "legacy migration" is what currently exists. Backwards compatibility is provided by a short python script which converts legacy to v2. Once the libxl changes are complete, xc_domain_save.c and xc_domain_restore.c can be deleted, along with other assorted bits and pieces. ~Andrew