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] Enlarge default NR_CPUS to 64 for x86_64

To: "Wei, Gang" <gang.wei@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Enlarge default NR_CPUS to 64 for x86_64
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 07 Aug 2009 17:18:23 +0100
Cc:
Delivery-date: Fri, 07 Aug 2009 09:19:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8FED46E8A9CA574792FC7AACAC38FE7701E7D9BEFD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoXQqZx2bBl8fi0SSC1Vq+dYQPArAAAhtahAAn4byAAA4L5yQ==
Thread-topic: [Xen-devel] [PATCH] Enlarge default NR_CPUS to 64 for x86_64
User-agent: Microsoft-Entourage/12.20.0.090605
On 07/08/2009 15:59, "Wei, Gang" <gang.wei@xxxxxxxxx> wrote:

> Not sure about whether we can raise it for i386 too. I am a little confused by
> below lines in config.h:
> 
>     #ifdef __i386__
>     #if NR_CPUS > 32
>     #error "Maximum of 32 physical processors supported by Xen on x86_32"
>     #endif
>     /* Maximum number of virtual CPUs in multi-processor guests. */
>     #define MAX_VIRT_CPUS XEN_LEGACY_MAX_VCPUS
>     #endif
> 
> I don't know why this compiling time error was put here for i386 yet. Any body
> know it?

I think it's a hangover from when there was a cpumask_t inside struct
page_info. That structure had to be fixed size for i386 to fit in the
hypervisor's virtual memory footprint.

 -- Keir



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