linux-kernel - Re: [PATCH][RFC] x86: add non x86 build configuration

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, 30 Oct 2008 21:57:12 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [PATCH][RFC] x86: add non x86 build configuration


* Steven Rostedt <rostedt@...dmis.org> wrote:

> 
> On Thu, 30 Oct 2008, Ingo Molnar wrote:
> 
> > 
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> > 
> > One important detail: could you please flip around the modality of the 
> > option? Right now it's CONFIG_SIMULATE_NON_X86_CONFIGURATION, and that 
> > will be set by allyesconfig. But it has the exact opposite effect of 
> > an "all yes" config.
> 
> Hmm, I made it a choice, with the "Normal Config" as default, so 
> that allyesconfig will not set it. Does it get set for you when you 
> do an allyesconfig?  I had to do the following:

hm, indeed.

Still ... the Kconfig glue looks a bit weird - it's almost never a 
good idea to put 'NOT' (or any other logic operator) into a config 
name. Why not make this CONFIG_STANDARD_X86_FEATURES and allow it to 
be disabled when CONFIG_EMBEDDED is enabled? This way it's not just a 
debug thing but also a kernel sizing feature.

	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/