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] My turn to rant about types... bitops

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] My turn to rant about types... bitops
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Wed, 5 Oct 2005 12:52:48 -0400
Cc: rusty@xxxxxxxxxxxxxxx
Delivery-date: Wed, 05 Oct 2005 16:50:26 +0000
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/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
I think around linux-2.4.19 (and thanks to rusty?) bitops.h went s/ void */unsigned long */, any chance is Xen following suit? The next request would be to change all arrays destined for bitops to be defined using unsigned long.
specifically:
    struct shared_info {
        [....]
        u32 evtchn_pending[32];
        u32 evtchn_mask[32];
    };

-JX


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