All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: New bluesmoke patch available, implements MCE-without-MCA support
Date: Wed, 15 Nov 2000 17:02:03 -0800	[thread overview]
Message-ID: <3A13320B.E5B47EF8@transmeta.com> (raw)
In-Reply-To: <200011160056.BAA20778@harpo.it.uu.se>

Mikael Pettersson wrote:
> 
> 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.)
> 

Actually, that's just fine.  It won't cause any harm; all that will mean
is that it will never raise #MC.  Remember that a CPU should, in proper
operation, never raise #MC anyway!

Their implementation is a legal (albeit useless) implementation of MCE. 
No need to special-case it.

	-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-16  1:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16  0:56 New bluesmoke patch available, implements MCE-without-MCA support Mikael Pettersson
2000-11-16  1:02 ` H. Peter Anvin [this message]
  -- 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=3A13320B.E5B47EF8@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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.