From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: test11-pre5, Athlon, and Machine Check Architecture
Date: 15 Nov 2000 13:34:20 -0800 [thread overview]
Message-ID: <8uuvgs$1u1$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011152107420.2791-100000@neo.local>
Followup to: <Pine.LNX.4.21.0011152107420.2791-100000@neo.local>
By author: davej@suse.de
In newsgroup: linux.dev.kernel
>
>
> > However, since at least AMD Athlon actually advertises MCA, I would
> > like to verify that the code works on these processors before
> > submitting it to Linus.
>
> The Athlon MCA is basically the same architecture-wise as Pentium Pro/II
> But there are some differences.. Until AMD make document 21656 (BIOS
> writers guide) public (or even a subset of it), we'll not be able to take
> advantage of these extra features.
>
> I'd suggest that until this happens, we leave bluesmoke.c Intel only.
>
That's completely the wrong way to look at it. AMD are certainly free
to add features, what they aren't free to do is making code that
expects the documented behaviour fail -- and if so, it's their bug. I
have so far gotten no indication that that is the case; the only thing
I have gotten so far is a positive report that it at least doesn't do
the wrong thing in the no-#MF case.
-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/
next prev parent reply other threads:[~2000-11-15 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 21:12 test11-pre5, Athlon, and Machine Check Architecture davej
2000-11-15 21:34 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 20:09 H. Peter Anvin
2000-11-15 21:14 ` Rogier Wolff
2000-11-15 21:32 ` 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='8uuvgs$1u1$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 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.