From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 cpu selection (first hack)
Date: Thu, 30 May 2002 19:20:13 -0400 [thread overview]
Message-ID: <3CF6B3AD.6010106@mandrakesoft.com> (raw)
In-Reply-To: <20020530225015.GA1829@werewolf.able.es>
J.A. Magallon wrote:
>- Make all and every cpu a checkbox, so you just say 'I want my kernel to
> support this and that CPU'. This kills the problem of the ordering, and
> adds one other advantage: you do not need to support intermediate CPUs,
> like 'i want my kernel to run ok on pentium-mmx (my firewall) and on
> p4 (my desktop). I will never run it on a PII, so do not include the
> hacks for PII'. And of course, 'If I run my p-mmx capable on a friend's
> PII and it eats his drive and burns his TV set, it is only _my_ fault'.
>
>Patch follows, comments are welcome. Next step is to begin to order the logic,
>but I wanted to ask first about this.
>
>
First cut seems like a good start...
Comments:
* use standard CML indentation
* use CONFIG_X86_ as the prefix for all config symbols you're creating
* Alan's comment seems fair, and also gives me a tangential idea: 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.
Jeff
next prev parent reply other threads:[~2002-05-30 23:22 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 [this message]
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
-- 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=3CF6B3AD.6010106@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=jamagallon@able.es \
--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