[<prev] [next>] [day] [month] [year] [list]
Message-Id: <E1KRp7q-0001pd-61@be1.7eggert.dyndns.org>
Date: Sat, 09 Aug 2008 16:08:57 +0200
From: Bodo Eggert <7eggert@....de>
To: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
michael@...e-electrons.com
Subject: Re: [PATCH 1/1] [x86] Configuration options to compile out x86 CPU support code
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com> wrote:
> This patch adds some configuration options that allow to compile out
> CPU vendor-specific code in x86 kernels (in arch/x86/kernel/cpu). The
> new configuration options are only visible when CONFIG_EMBEDDED is
> selected, as they are mostly interesting for space savings reasons.
> +menuconfig PROCESSOR_SELECT
> + default y
> + bool "Supported processor vendors" if EMBEDDED
> + help
> + This lets you choose what x86 vendor support code your kernel
> + will include.
> +
> +config CPU_SUP_INTEL_32
> + default y
> + bool "Support Intel processors" if PROCESSOR_SELECT
> + depends on !64BIT
> + help
> + This enables extended support for Intel processors
> +
I don't think having a generic kernel for only Intel CPUs makes much sense,
and OTOH, if you optimize for e.g. Athlon CPUs, you're likely to not need
Intel code on that machine - even on desktop systems.
What about an option to "Include code for CPUs from all supported vendors",
invisible and y for generic kernels?
--
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