From: Dave Jones <davej@suse.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 cpu selection (first hack)
Date: Fri, 31 May 2002 01:42:24 +0200 [thread overview]
Message-ID: <20020531014224.C9282@suse.de> (raw)
In-Reply-To: <20020530225015.GA1829@werewolf.able.es> <3CF6B3AD.6010106@mandrakesoft.com>
On Thu, May 30, 2002 at 07:20:13PM -0400, Jeff Garzik wrote:
> wonder if making the CPU features selectable is useful? i.e. provide an
> actual config option for MMX memcpy, F00F bug, WP, etc. Normal (current)
> logic is to look at the cpu selected, and deduce these options.
J.A's comment that most people compiling kernels shouldn't need to know
what bugs their CPU has before they pick it is a good one imo[1]
Also an explosion of CONFIG_ items where they can be sanely derived
from others doesn't make much sense imo.
Dave.
[1] fsck, I sound like Eric.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-05-30 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 22:50 [PATCH] x86 cpu selection (first hack) J.A. Magallon
2002-05-30 23:20 ` Jeff Garzik
2002-05-30 23:42 ` Dave Jones [this message]
2002-05-31 0:36 ` J.A. Magallon
2002-05-31 0:05 ` Alan Cox
2002-05-30 23:15 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2002-05-31 0:07 Leif Sawyer
2002-05-31 0:12 ` Jeff Garzik
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=20020531014224.C9282@suse.de \
--to=davej@suse.de \
--cc=jamagallon@able.es \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/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