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-ia64-devel

RE: [Xen-ia64-devel] [PATCH] Cleanup hypercall.h

To: "Alex Williamson" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] Cleanup hypercall.h
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 28 Feb 2006 10:30:33 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 28 Feb 2006 02:30:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcY8DbxA+7WrMb3STZqIaCl/HeQ/oQAABh+A
Thread-topic: [Xen-ia64-devel] [PATCH] Cleanup hypercall.h
>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>Sent: 2006年2月28日 10:18
>>      BTW, how often do you plan to ask for pull xen-ia64-unstable into
>> xen-unstable?
>
>Hi Kevin,
>
>   Thanks for the new patch.  Dan and I were talking about when we
>should pull xen-ia64 into xen-unstable this afternoon.  I was planning
>on syncing and trying to get that done this week, but xen-unstable
>doesn't build currently on ia64 and I suspect won't until we update to
>2.6.16-rcX (fails on cpu_sibling_map for me).  I'll see if I can make
>any progress on that, but if anyone else gets to it first, please send
>on your progress.  Thanks,
>
>       Alex

Seems it's similar issue as previous one (cpu_online_map). For x86,
 CONFIG_SMP is the base and always on, so it's very likely for 
common code to access variables defined only under CONFIG_SMP. 
Should we enable CONFIG_SMP by default, once it gets more stable?

Tristan, how about your opinion? Is it time for changing that now?

Thanks,
Kevin

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