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: Valdis.Kletnieks@vt.edu, 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 17:21:20 +0100	[thread overview]
Message-ID: <20090102162120.GG1180@elte.hu> (raw)
In-Reply-To: <3f9a31f40901020813t136ad2ceif1092f312866a0ce@mail.gmail.com>


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

> On Fri, Jan 2, 2009 at 9:09 PM,  <Valdis.Kletnieks@vt.edu> wrote:
> > On Fri, 02 Jan 2009 20:40:16 +0530, Jaswinder Singh Rajput said:
> >
> >> If I know what is my CPU there is no point for supporting all related
> >> CPUs in my kernel.
> >
> > EMBEDDED is for a large assortment of things, all of which are of the form:
> >
> > General users won't want to change Y, but if I know I don't need Y, there is
> > no point in supporting Y in the kernel.
> >
> 
> On 64 bit AMD machine I was getting :
> [    0.000000] KERNEL supported cpus:
> [    0.000000]   Intel GenuineIntel
> [    0.000000]   AMD AuthenticAMD
> [    0.000000]   Centaur CentaurHauls
> 
> By using the following patch I get rid of extra CPU support and also 
> reduces size of the kernel.

So you want to save kernel size by making less generic kernels tailored to 
a single box [yours in this case] - basically embedding the kernel on it?

> Let me know why should I choose EMBEDDED option ? I know I am not using 
> Embbeded machine and I do not need embbeded features on my machine. 
> [...]

that is what CONFIG_EMBEDDED=y means in broad terms: "make the kernel more 
specific [more embedded] to a particular hw/sw combination".

	Ingo

  parent reply	other threads:[~2009-01-02 16:21 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
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 [this message]
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=20090102162120.GG1180@elte.hu \
    --to=mingo@elte.hu \
    --cc=Valdis.Kletnieks@vt.edu \
    --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