linux-kernel - Re: [PATCH] x86: allow 8 more cpus could be used

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090129230827.GA29611@elte.hu>
Date:	Fri, 30 Jan 2009 00:08:27 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: allow 8 more cpus could be used


* Yinghai Lu <yinghai@...nel.org> wrote:

> Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@...nel.org> wrote:
> > 
> >> Impact: fix left out MARCO
> >>
> >> X86_PC will be always enabled. so need to check if we have bigsmp 
> >> support built in before cut off more than 8 cpus.
> > 
> > ah, that's a leftover reference to X86_PC. It can now be removed, together 
> > with the Kconfig X86_PC option.
> > 
> >> -#if defined(CONFIG_X86_PC) && defined(CONFIG_X86_32)
> >> +#if defined(CONFIG_X86_PC) && !defined(CONFIG_X86_BIGSMP)
> >>  	if (def_to_bigsmp && nr_cpu_ids > 8) {
> >>  		unsigned int cpu;
> >>  		unsigned nr;
> > 
> > Could you please send a patch that removes both X86_PC and X86_BIGSMP - 
> > and removes the above cutoff code too, so that it will be built-in all the 
> > time?
> 
> sure. maybe we could keep X86_BIGSMP for a while. So someone don't 
> enable BIGSMP for small system?

yeah, we can certainly keep it - the code to conditionalize it is there 
and isnt causing problems really.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/