From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.xen@gmail.com>
Subject: Re: [PATCH 0 of 2] RFC: hvm_save backwards compatibility
Date: Fri, 01 Apr 2011 11:23:02 +0100
Message-ID: <C9BB6616.15B11%keir.xen@gmail.com>
References: <patchbomb.1301581299@elijah>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <patchbomb.1301581299@elijah>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xensource.com
Cc: Tim Deegan <Tim.Deegan@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 31/03/2011 15:21, "George Dunlap" <george.dunlap@eu.citrix.com> wrote:

> This patch series introduces the ability to be backwards-compatible
> with previous versions of hvm_save structures.  The first patch
> introduces the compatibility code; the second takes advantage of it
> to allow Xen to handle hvm_hw_cpu entries from before Xen 4.0.

Ends up with quite a bit of struct duplication, but maybe that's still the
clearest and best way. Anyhow, I'll let Tim Ack and apply these. If they
look okay we can then backport to the 4.1 and 4.0 branches.

 Thanks,
 Keir

> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel