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] sizeof(long) different under windows x64 and linux x64

To: Andy Grover <andy.grover@xxxxxxxxxx>, James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] sizeof(long) different under windows x64 and linux x64
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 23 Jan 2008 08:00:40 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 23 Jan 2008 00:01:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1201045195.2837.37.camel@xxxxxxxxxxxxxxxxxxxxx>
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: AchdlguISegjpsmJEdyR5wAWy6hiGQ==
Thread-topic: [Xen-devel] sizeof(long) different under windows x64 and linux x64
User-agent: Microsoft-Entourage/11.3.6.070618
On 22/1/08 23:39, "Andy Grover" <andy.grover@xxxxxxxxxx> wrote:

>> Are the xen header files written with the assumption that sizeof(long) =
>> 8? If so, this would explain why i'm getting EINVAL from the hypervisor
>> under windows x64...
> 
> I think it's very hard to be LP64/LLP64-clean without actual testing on
> both.
> 
> I'm sure patches would be accepted to clean things up. We imported a
> private version of the xen headers into the winpv tree hg so maybe we
> should just go ahead and modify that, and then we can pull out a diff to
> submit against xen-unstable when we know all the issues are cleaned up?

Maybe. I don't see why people are worried about having privately diverged
copies of the headers for their own target environment though. They're not
going to magically become incompatible with future versions of Xen. You need
only update your private headers, and then only incrementally, when you want
to use new features of future Xen versions.

 -- Keir



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