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

[Xen-devel] Re: One question on mcinfo_extended

To: <yunhong.jiang@xxxxxxxxx>
Subject: [Xen-devel] Re: One question on mcinfo_extended
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 20 Apr 2010 09:38:33 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Apr 2010 01:39:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The point of using void* here is that even in a 32-bit Dom0 running on 64-bit 
Xen should have access to all registers - I couldn't think of anything better 
back then. The implication is that Dom0 side code must be prepared to deal with 
that - which I think isn't the case at present.

Jan

>>> "Jiang, Yunhong"  04/20/10 10:20 AM >>>
Hi, Jan, in 19465 changeset, the mcinfo_extended's mc_msr is changed to be an 
array of sizeof(void *) * 4. I assume your purpose is to make it works on both 
32 and 64. But will it cause trouble to compatibility mode dom0? Especially if 
dom0 copy the information to local variable, and loop the variable through 
mcinfo_extended->mc_msrs?

Thanks
--jyh


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

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