From: "H. Peter Anvin" <hpa@transmeta.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: CPU detection revamp (Request for comments)
Date: Thu, 09 Nov 2000 19:17:36 -0800 [thread overview]
Message-ID: <3A0B68D0.EB344C71@transmeta.com> (raw)
Hi guys,
I wanted to give you a preview of the CPUID revision patch; it is not
100% ready yet in that (a) it still has a bunch of debugging printk() and
(b) I haven't ported over mtrr.c yet.
This code took a lot longer to write than I had expected, mostly because
I kept running into various forms of bugs with the *old* code. In fact,
it looks like some of the bugs involving CPUID feature flags in the past
have been due to the inconsistent handling of these flags in Linux. I
believe the new code should be a lot better in this aspect, and should
avoid bugs as much as possible.
I would very much like this code to be tested and get success/fail
reports on various CPUs, *especially* AMD (Athlon especially) and Cyrix
chips.
As I mentioned, you will have to compile without MTRR support in this
version. I should have that fixed soon.
The patch is at:
ftp://ftp.kernel.org/pub/linux/kernel/people/hpa/cpuid-2.4.0-test11-pre2-1.diff
In case of success, please send me the output of the new /proc/cpuinfo on
your system. In case of failure, please compile and run the following
program and send me the output, as well as /proc/cpuinfo from an
unpatched kernel version:
ftp://ftp.kernel.org/pub/linux/kernel/people/hpa/cpuid.c
Many thanks,
-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 3:18 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=3A0B68D0.EB344C71@transmeta.com \
--to=hpa@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.