[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 0 of 2] RFC: hvm_save backwards compatibility
- To: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <keir.xen@xxxxxxxxx>
- Date: Fri, 01 Apr 2011 11:23:02 +0100
- Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
- Delivery-date: Fri, 01 Apr 2011 03:23:52 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=aKRG1rKViFKaGIabKVp/ddho++0DJqNCYXb1JALvSXTDlnYv10xkwvUlZYpGUlUgAj SvjvKuLnkl1M3Dptkl46TzZjurGw0RZ/nbEirc+QHUnJdi5sHpg0TPHJVMmzJim5/Ola qOecyQFIXahZNO7D8iFRmhdR4GXFjWT91gGJc=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcvwVsfKXtSRNmMRk0qJsIVGM1EHXA==
- Thread-topic: [Xen-devel] [PATCH 0 of 2] RFC: hvm_save backwards compatibility
On 31/03/2011 15:21, "George Dunlap" <george.dunlap@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
