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

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:	Fri, 6 Jun 2008 16:09:47 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	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: make generic arch support NUMAQ v2

* Yinghai Lu <yhlu.kernel@...il.com> wrote:

> > It is my understanding that special support for NUMAQ should die, so 
> > the only remaning usage of CONFIG_NUMAQ is if set to select 
> > GENERICARCH. In other words that you should not use CONFIG_NUMAQ 
> > anywhere in the code but solely rely on GENERICARCH and then do 
> > runtime detection of the other things.
> 
> in case someone don't want to build that special numaq code in.
> 
> I think we should make ES7000, Summit depend to GENERICARCH too.

correct. If someone wants more restricted support, pure CONFIG_X86_PC 
should do that fine.

also, even GENERICARCH should have as little Kconfig implications as 
possible. I.e. before your cleanups the subarch code was used to 
implement something very non-PC, and it was done build-time - which is a 
PITA in terms of testing and in terms of general complexity. We want to 
remove those complications and eventually we want to remove the subarch 
code altogether. (without narrowing hw support of course)

	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/