From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: [i386] CPU detection cleanup version 2
Date: 9 Nov 2000 22:55:51 -0800 [thread overview]
Message-ID: <8ug65n$53t$1@cesium.transmeta.com> (raw)
I have produced another version of the CPU detection cleanup patch.
Now I have ported over mtrr.c, and fix a small handful of places I had
missed because of the configurations I had used.
The number one thing I *haven't* yet done with it -- which I'd like to
-- is to integrate the handling of bugs (except the P6 SEP bug) into
the same framework and pretty much eliminate asm/bugs.h, as well as
splitting off the CPU detection into a separate file. However, due to
the very late stage in the game, I wanted to worry about things that
are important for correctness for now.
Please do keep in mind this is not merely a cosmetic change. The old
code was rather shockingly klugy and incorrect in a number of places.
A lot of problems I thought were AMD CPUID bugs were in fact caused by
Linux trying to use the Intel-defined and the AMD-defined flags as
interchangeable (they're not.)
The patch is at:
ftp://ftp.kernel.org/pub/linux/kernel/people/hpa/cpuid-2.4.0-test11-pre2-2.diff
Please give me reports on works/not works with output from
/proc/cpuinfo and the cpuid.c program (in the same directory as the
patch.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-10 6:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='8ug65n$53t$1@cesium.transmeta.com' \
--to=hpa@zytor.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