From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Bryan Donlan" <bdonlan@gmail.com>,
"Ingo Brueckl" <ib@wupperonline.de>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: x86 (Linux Tiny): configure out support for some processors
Date: Fri, 2 Jan 2009 20:40:16 +0530 [thread overview]
Message-ID: <3f9a31f40901020710h508bbfbch3d7ccd6f4898ea03@mail.gmail.com> (raw)
In-Reply-To: <20090102093801.GD1975@elte.hu>
On Fri, Jan 2, 2009 at 3:08 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jaswinder Singh Rajput <jaswinderlinux@gmail.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.
next prev parent reply other threads:[~2009-01-02 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 20:37 Ingo Brueckl
2009-01-02 5:19 ` Bryan Donlan
2009-01-02 5:59 ` Jaswinder Singh Rajput
2009-01-02 9:38 ` Ingo Molnar
2009-01-02 15:10 ` Jaswinder Singh Rajput [this message]
2009-01-02 15:39 ` Valdis.Kletnieks
2009-01-02 16:13 ` Jaswinder Singh Rajput
2009-01-02 16:20 ` Valdis.Kletnieks
2009-01-02 16:23 ` Ingo Molnar
2009-01-02 16:21 ` Ingo Molnar
2009-01-02 16:38 ` Jaswinder Singh Rajput
2009-01-02 17:34 ` Ingo Molnar
2009-01-02 18:13 ` Replace CONFIG_EMBEDDED [Was: x86 (Linux Tiny): configure out support for some processor] Sam Ravnborg
2009-01-02 19:02 ` Bill Davidsen
2009-01-02 19:31 ` Sam Ravnborg
2009-01-02 16:51 ` x86 (Linux Tiny): configure out support for some processors david
2009-01-02 16:26 ` Valdis.Kletnieks
2009-01-02 18:54 ` david
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f9a31f40901020710h508bbfbch3d7ccd6f4898ea03@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=bdonlan@gmail.com \
--cc=hpa@zytor.com \
--cc=ib@wupperonline.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome