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 20:40:16 +0530
From:	"Jaswinder Singh Rajput" <jaswinderlinux@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"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, Jan 2, 2009 at 3:08 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Jaswinder Singh Rajput <jaswinderlinux@...il.com> wrote:
>>
>> I think EMBEDDED is a misnomer for using CONFIG_PROCESSOR_SELECT and
>> should be used for more specific to Embedded stuff like for Embedded
>> range of CPUs or Embedded Systems.
>
> i think EMBEDDED is justified in this particular case, as enabling
> CONFIG_PROCESSOR_SELECT allows you to create truly CPU-incompatible
> kernels. Kernels that panic on bootup on contemporary CPUs that happen to
> have a different manufacturer.
>

EMBEDDED leads to following options :
Configure standard kernel features (for small systems)
[*]   Enable 16-bit UID system calls (NEW)
[*]   Sysctl syscall support (NEW)
[*]   Load all symbols for debugging/ksymoops (NEW)
[*]     Include all symbols in kallsyms
[*]       Strip machine generated symbols from kallsyms
[*]     Do an extra kallsyms pass
[*]   Support for hot-pluggable devices (NEW)
[*]   Enable support for printk (NEW)

and these are perfect options for Embedded.

But selection of the PROCESSOR based on EMBEDDED is not a good logic.

CONFIG_PROCESSOR_SELECT should be an independent and by default should
select all related CPUs but user can specify its own CPU if he wants.

If I know what is my CPU there is no point for supporting all related
CPUs in my kernel.

This needs to be fixed.

Thank you,

JSR.
--
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/