mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: New bluesmoke patch available, implements MCE-without-MCA support
Date: Thu, 16 Nov 2000 01:56:09 +0100 (MET)	[thread overview]
Message-ID: <200011160056.BAA20778@harpo.it.uu.se> (raw)

On 15 Nov 2000, H. Peter Anvin wrote:

>This implements support for MCE on chips which don't support MCA (in
>addition to enabling MCA for non-Intel chips, like Athlon, which
>supports MCA.)
>
>I would appreciate it if people who have chips with MCE but no MCA --
>this includes older AMD chips and some Cyrix chips at the very least
>-- would please be so kind and try this out.

I have a K6-III which announces MCE but not MCA, so I was going to
test this on that machine.

However, both the K6-III manual and the K6 BIOS guide state quite
clearly that the K6 family only has a "stub" MCE implementation.
The MCE capability is announced, there are two MCE-related MSRs,
and there is a CR4.MCE flag, but none of it actually _does_ anything.

The new CPU detection code should probably clear FEATURE_MCE for K6 CPUs.
(We might consider it an AMD bug, but in their defense, they do state
that the stub implementation was done for "compatibility" reasons.)

/Mikael
-
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-16  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16  0:56 Mikael Pettersson [this message]
2000-11-16  1:02 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2000-11-15 21:37 H. Peter Anvin
2000-11-15 21:57 ` H. Peter Anvin
2000-11-16 14:08 ` Maciej W. Rozycki

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=200011160056.BAA20778@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=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

all inboxes | Powered by JetHome®