linux-kernel - Re: RFC [PATCH] x86: make generic arch support NUMAQ

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]

Date:	Thu, 5 Jun 2008 14:39:33 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	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: RFC [PATCH] x86: make generic arch support NUMAQ


* Sam Ravnborg <sam@...nborg.org> wrote:

> > +#if defined(CONFIG_X86_NUMAQ) || defined(CONFIG_X86_GENERICARCH)
> 
> I counted several places where you test for the above. Introducing a 
> CONFIG_X86_NUMAQ_OR_GENERIC would simplify stuff.

Yinghai, please get rid of the NUMAQ build option altogether and 
eliminate the subarch.

We should keep a compatibility CONFIG_X86_NUMAQ that selects 
X86_GENERICARCH, so that 'make oldconfig' on a NUMAQ config does the 
right thing - but it's not a subarch anymore nor anything 
user-configurable.

All that together would be a very nice simplification.

	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/