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] [PATCH] [pv-ops domU] support MAXSMP

To: "Andrew Jones" <drjones@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [pv-ops domU] support MAXSMP
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 18 Dec 2009 10:07:09 +0000
Cc: jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Dec 2009 02:06:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B2B4BF3.1010507@xxxxxxxxxx>
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: <4B2B4BF3.1010507@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Andrew Jones <drjones@xxxxxxxxxx> 18.12.09 10:31 >>>
>The MAXSMP config option requires CPUMASK_OFFSTACK, which in turn
>requires we init the memory for the maps while we bringing up the cpus.
>MAXSMP also increases NR_CPUS to 4096. This increase in size exposed an
>issue in the argument construction for mulitcalls from
>xen_flush_tlb_others. The args should only need space for the actual
>number of cpus, which with xen is currently only up to 32.

I don't think new code should be making assumptions like this anymore,
since Xen already supports higher numbers (it's merely the tools which
so far don't). You're basically trading a compile time detectable large
value on stack for one that can grow large dynamically (and hence
require quite a bit more effort to debug, should it ever overrun the
stack).

Jan


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