[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] [PATCH] Enlarge default NR_CPUS to 64 for x86_64
> 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. FYI, xen/include/asm-x86/mm.h still #includes <xen/cpumask.h> and that include can be removed now (compile tested only). > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] > Sent: Friday, August 07, 2009 10:18 AM > To: Wei, Gang; xen-devel@xxxxxxxxxxxxxxxxxxx > Subject: Re: [Xen-devel] [PATCH] Enlarge default NR_CPUS to 64 for > x86_64 > > > 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 > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |