[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f9a31f40901020813t136ad2ceif1092f312866a0ce@mail.gmail.com>
Date: Fri, 2 Jan 2009 21:43:03 +0530
From: "Jaswinder Singh Rajput" <jaswinderlinux@...il.com>
To: Valdis.Kletnieks@...edu
Cc: "Ingo Molnar" <mingo@...e.hu>, "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 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.
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. If I am willing to go North why should I go South first ?
--- a/arch/x86/Kconfig.cpu
+++ b/arch/x86/Kconfig.cpu
@@ -411,7 +411,7 @@ config X86_DEBUGCTLMSR
depends on !(MK6 || MWINCHIPC6 || MWINCHIP3D || MCYRIXIII ||
M586MMX || M586TSC || M586 || M486 || M386)
menuconfig PROCESSOR_SELECT
- bool "Supported processor vendors" if EMBEDDED
+ bool "Supported processor vendors"
help
This lets you choose what x86 vendor support code your kernel
will include.
--
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