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] RFC: 32 bits as smallest atomic size.

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: 32 bits as smallest atomic size.
From: "Ronald G. Minnich" <rminnich@xxxxxxxx>
Date: Mon, 28 Mar 2005 08:37:23 -0700 (MST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Delivery-date: Tue, 29 Mar 2005 06:59:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4f43c2736fa6b4f9c86600c5308c822f@xxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <16964.33214.921809.324278@xxxxxxxxxxxxxxxxxxxxx> <74f362598b4e1a0d46aacb1a514706ac@xxxxxxxxxxxx> <16964.41853.43756.836319@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0503261029270.23670@xxxxxxxxxxxxxxx> <16965.40068.388024.929154@xxxxxxxxxxxxxxxxxxxxx> <21eeeb49a66395420f0c47c7d5327630@xxxxxxxxxxxx> <2330d67d198017769ff97ec4a548dcf2@xxxxxxxxxxxx> <Pine.LNX.4.58.0503262030500.24687@xxxxxxxxxxxxxxx> <b44b561aa3958105c8613c6364b6a6da@xxxxxxxxxxxx> <4f43c2736fa6b4f9c86600c5308c822f@xxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx

On Sun, 27 Mar 2005, Keir Fraser wrote:

> Already the field offset comments are broken in a few places in unstable, so
> perhaps this is a better way to go.

it's an idea.  A few years ago I wrote drivers for SCI and had a mixed 
linux/alpha freebsd/pentium cluster. It's a little tricky to get everyone 
happily addressing each other's memories across that boundary, but I did 
it by making all struct fields unsigned long long and letting the 
compilers do the right thing. I didn't use a single __attribute__ 
directive, but at the same time, these fairly different machines with 
different OSes had shared memory. I still don't see why xen can not do the 
same.

ron


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel