From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Subject: Re: 32/64-bit hypercall interface Date: Fri, 30 Sep 2005 12:44:27 -0400 Message-ID: <433D6B6B.3030906@bsdlazarus.com> References: <200509291317.25090.hollisb@us.ibm.com> <200509291512.29891.hollisb@us.ibm.com> <31c4b41b23a195dd2d69cdea28754843@cl.cam.ac.uk> <20050930005405.GG5242@andreilx.eng.hq.xensource.com> <24aa8891a52e3d3a34fc3b59179a8d0f@us.ibm.com> <99da46303de5c070b985b66e5c1c96dd@cl.cam.ac.uk> <4f11a9f98b8a256a1a9011af12e9788e@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4f11a9f98b8a256a1a9011af12e9788e@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Hollis Blanchard , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi, > > I think the Linux kernel folks learned the "unsigned long" lesson too > late, and now there is quite a lot of fixup code to convert 32-bit > userspace structs to 64-bit kernel structs (have a look at > linux/fs/compat_ioctl.c and compat.c). It seems a shame to repeat the > same mistakes in Xen... > Quick question.... What is this "'unsigned long' lesson" you are refering to? -- David