From: Bodo Eggert <7eggert@gmx.de>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
tglx@linu
Subject: Re: [PATCH 1/1] [x86] Configuration options to compile out x86 CPU support code
Date: Sat, 09 Aug 2008 16:08:57 +0200 [thread overview]
Message-ID: <E1KRp7q-0001pd-61@be1.7eggert.dyndns.org> (raw)
In-Reply-To: aXrl4-2FX-1@gated-at.bofh.it
Thomas Petazzoni <thomas.petazzoni@free-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?
next parent reply other threads:[~2008-08-09 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030410181011$6d15@gated-at.bofh.it>
[not found] ` <aXrl4-2FX-1@gated-at.bofh.it>
2008-08-09 14:08 ` Bodo Eggert [this message]
2008-08-05 9:45 [PATCH 1/1] [x86] Configuration options to compile out x86 CPU support code Thomas Petazzoni
2008-08-15 14:18 ` Ingo Molnar
2008-08-15 14:38 ` Ingo Molnar
2008-08-15 20:36 ` H. Peter Anvin
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=E1KRp7q-0001pd-61@be1.7eggert.dyndns.org \
--to=7eggert@gmx.de \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linu \
--cc=thomas.petazzoni@free-electrons.com \
/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;
as well as URLs for NNTP newsgroup(s).