[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090102162120.GG1180@elte.hu>
Date: Fri, 2 Jan 2009 17:21:20 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc: Valdis.Kletnieks@...edu, 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
* Jaswinder Singh Rajput <jaswinderlinux@...il.com> wrote:
> On Fri, Jan 2, 2009 at 9:09 PM, <Valdis.Kletnieks@...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
--
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/
Powered by blists - more mailing lists