linux-kernel - Re: x86 (Linux Tiny): configure out support for some processors

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, 2 Jan 2009 10:54:15 -0800 (PST)
From:	david@...g.hm
To:	Valdis.Kletnieks@...edu
cc:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	Ingo Molnar <mingo@...e.hu>, Bryan Donlan <bdonlan@...il.com>,
	Ingo Brueckl <ib@...peronline.de>,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86 (Linux Tiny): configure out support for some processors

On Fri, 2 Jan 2009, Valdis.Kletnieks@...edu wrote:

> On Fri, 02 Jan 2009 08:51:28 PST, david@...g.hm said:
>> having things outside of the embedded menu depend on embedded makes it
>> hard for people to figure out what they need to do to disable specific
>> things.
>
> Odd, I can do a 'make menuconfig', do a /EARLY_PRINTK, and see:
>
> Symbol: EARLY_PRINTK [=y]                                               x
>  x Prompt: Early printk                                                    x
>  x   Defined at arch/x86/Kconfig.debug:33                                  x
>  x   Depends on: EMBEDDED                                                  x
>  x   Location:                                                             x
>  x     -> Kernel hacking
>
>> if you follow the logic you are providing to it's logical conclusion you
>> may as well put all kernel config options under "I really know what I'm
>> doing" top level lockout
>
> Hey, I didn't make up that logic. ;)
>
> A large percentage of the kernel config options are things that really *could*
> be one way or the other for any given system.  Maybe you want ext4, maybe you
> don't.  Maybe you need process accounting, maybe you don't.  So they don't go
> under EMBEDDED.  But we can be 98% sure that they probably want PRINTK.

is there an easy way to pull the list of what symbols depend on EMBEDDED?

David Lang
--
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/