public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
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 10:38:01 +0100	[thread overview]
Message-ID: <20090102093801.GD1975@elte.hu> (raw)
In-Reply-To: <3f9a31f40901012159l255b95a8he41a341f36ebc54e@mail.gmail.com>


* Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:

> On Fri, Jan 2, 2009 at 10:49 AM, Bryan Donlan <bdonlan@gmail.com> wrote:
> > On Thu, Jan 1, 2009 at 3:37 PM, Ingo Brueckl <ib@wupperonline.de> wrote:
> >> Is there any reason why CONFIG_PROCESSOR_SELECT is limited to EMBEDDED only?
> >>
> >> In my desktop pc is one specific cpu only, so I do not need support for the
> >> other processors. Unfortunately, I have no chance to disable the other ones.
> >>
> >> As it is already configurable, why not giving this option to everyone?
> >
> > EMBEDDED is just a switch to enable configuration options related to 
> > removing 'core' features of the kernel to save space. Think of it as a 
> > safety to avoid accidentally turning off something important. Feel 
> > free to switch on EMBEDDED if you want to use CONFIG_PROCESSOR_SELECT 
> > - just enabling EMBEDDED doesn't do anything by itself.
> 
> 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.

The normal CPU selection options (like CONFIG_MCORE2) are more like 
performance and preference hints not hard constraints - those kernels will 
generally still boot fine on most other CPUs as well. (with a few 
common-sense exceptions like booting on truly ancient CPUs, i.e. booting 
an CONFIG_MCORE2 kernel on an i486DX CPU will not work)

	Ingo

  reply	other threads:[~2009-01-02  9:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 20:37 x86 (Linux Tiny): configure out support for some processors Ingo Brueckl
2009-01-02  5:19 ` Bryan Donlan
2009-01-02  5:59   ` Jaswinder Singh Rajput
2009-01-02  9:38     ` Ingo Molnar [this message]
2009-01-02 15:10       ` Jaswinder Singh Rajput
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=20090102093801.GD1975@elte.hu \
    --to=mingo@elte.hu \
    --cc=bdonlan@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ib@wupperonline.de \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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