WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH] make shared_info architecture independent

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, "He, Qing" <qing.he@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] make shared_info architecture independent
From: "Yang, Xiaowei" <xiaowei.yang@xxxxxxxxx>
Date: Fri, 1 Dec 2006 16:17:04 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Dec 2006 00:18:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccVGu7nChRh+annQ3K+gw6B+Sr5ogABG3+CAAAMt9A=
Thread-topic: [Xen-devel] [PATCH] make shared_info architecture independent
>Breaks ABI compatibility, and Jan Beulich's PV-PAE-on-64 patches can be
>extended for the HVM case.
>
Keir,
I don't quite understand what "break ABI compatibility" mean? Doesn't it
mean old domX kernel can't run with new HV or vice versa? Since we only
made a small change to evtchn structure inside and exported APIs is
untouched, we think it won't affect others.

Thanks, 
Xiaowei

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

<Prev in Thread] Current Thread [Next in Thread>