From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Leif Sawyer <lsawyer@gci.com>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
"J.A. Magallon" <jamagallon@able.es>, Dave Jones <davej@suse.de>
Subject: Re: [PATCH] x86 cpu selection (first hack)
Date: Thu, 30 May 2002 20:12:57 -0400 [thread overview]
Message-ID: <3CF6C009.6040206@mandrakesoft.com> (raw)
In-Reply-To: <BF9651D8732ED311A61D00105A9CA31508EC0CD6@berkeley.gci.com>
Leif Sawyer wrote:
>Dave Jones replied to
>
>
>>Jeff Garzik who wrote:
>>
>>
>>
>>>[I] 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
>>
>>
>>
>
>Perhaps a comprimise could be made?
>
>Envision a config option where you would have 'expert' choices
>for MMX, FOOF, WP, etc.
>
>
Well... let's rein in the horses. Before we go too far down this road,
I would rather that we just get one thing, individual cpu selection,
correct. After that, we can look at making processor features
selectable, or grouping cpus based on "expert" details like lack of WP
or supporting TSC.
Jeff
next prev parent reply other threads:[~2002-05-31 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 0:07 [PATCH] x86 cpu selection (first hack) Leif Sawyer
2002-05-31 0:12 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 22:50 J.A. Magallon
2002-05-30 23:20 ` Jeff Garzik
2002-05-30 23:42 ` Dave Jones
2002-05-31 0:36 ` J.A. Magallon
2002-05-31 0:05 ` Alan Cox
2002-05-30 23:15 ` J.A. Magallon
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=3CF6C009.6040206@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=davej@suse.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=lsawyer@gci.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