From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH v5 RFC 03/14] [HACK] tools/libxc: save/restore v2 framework Date: Tue, 17 Jun 2014 17:17:27 +0100 Message-ID: <53A06A17.8090903@citrix.com> References: <1402510482-21099-1-git-send-email-andrew.cooper3@citrix.com> <1402510482-21099-4-git-send-email-andrew.cooper3@citrix.com> <1403020821.25771.10.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1403020821.25771.10.camel@kazak.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: Ian Campbell Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On 17/06/14 17:00, Ian Campbell wrote: > On Wed, 2014-06-11 at 19:14 +0100, Andrew Cooper wrote: >> For testing purposes, the environmental variable "XG_MIGRATION_V2" allows the >> two save/restore codepaths to coexist, and have a runtime switch. >> >> It is indended that once this series is less RFC, the v2 framework will >> completely replace v1. > When do you imagine that will be? It seems to me like it could/should > reasonably happen now. > > > When I have some plausible libxl compatibility in the series, which is still ongoing work. If this were to be done in two parts, we would end up with a single identifiable xl stream containing possibly the new or possibly the old libxc stream, which makes backwards compatibility much harder to retrofit. ~Andrew