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

tmem 32-on-64 needs (Re: [Xen-devel] [PATCH] tmem cleanup)

To: <dan.magenheimer@xxxxxxxxxx>
Subject: tmem 32-on-64 needs (Re: [Xen-devel] [PATCH] tmem cleanup)
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 15 Jun 2009 15:09:26 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 15 Jun 2009 07:09:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A366CFA0200007800005B2B@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/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>
References: <4A366CFA0200007800005B2B@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> "Jan Beulich" <JBeulich@xxxxxxxxxx> 15.06.09 15:47 >>>
>- don't mis-use guest handle for passing an MFN value
>- eliminate unnecessary (and misplaced) use of XEN_GUEST_HANDLE_64
>- use copy_from_guest() instead of __copy_from_guest() for loading the
>  argument structure

I ran across these when looking at what changes 32-on-64 support for tmem
would require. However, there's another issue that I didn't feel like 
immediately
sending a patch out for: xen/include/public/tmem.h uses anonymous unions
and structures - all other public headers (with the exception of the declaration
of xenpf_set_processor_pminfo and xen_sysctl_pm_op, which probably are
mistakes/oversights) avoid this (or use it only when it is known to be only
compiled with gcc)) as being a non-standard feature, and the compatibility
header generation script depends on all compound types' fields to be named.

I realize that this will require changes on the client side too, which is why I
first wanted to see if there's anything that I'm overlooking.

Jan


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