From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Algorithm for CPU_X86
Date: Tue, 4 Jun 2002 05:18:40 +0200 [thread overview]
Message-ID: <20020604031840.GA4289@werewolf.able.es> (raw)
Hi all...
Following with the cpu selection changes, setting the flags controlled
by the various CPU_X86_xxxx can be a real mess.
But, I have ralized that those CPU_X86 flags can be logically split in
two groups: features (TSC,MMX,3DNOW) and bugfixes (PPRO_FENCE) (or perhaps
more, it is just a first thought...).
So the algorithm can be easy (i think..)
- Enable all feature flags (say, MMX and 3DNOW)
- Disable all bugfix flags (FENCE)
- For each CPU
if it does not have the feature, kill it
(if VENDOR_INTEL set 3DNOW=n)
if this-cpu-kernel could run on buggy-cpu, enable fix
(if GENERIC_586 set FENCE=y)
Right ?
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre9-jam1 #1 SMP lun jun 3 19:59:12 CEST 2002 i686
next reply other threads:[~2002-06-04 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 3:18 J.A. Magallon [this message]
2002-06-04 4:28 ` Algorithm for CPU_X86 Ghozlane Toumi
2002-06-04 5:19 ` 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=20020604031840.GA4289@werewolf.able.es \
--to=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