public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: thockin@hockin.org
To: Tim Small <tim@buttersideup.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Ong, Soo Keong" <soo.keong.ong@intel.com>,
	"Gross, Mark" <mark.gross@intel.com>,
	bluesmoke-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>,
	"Carbonari, Steven" <steven.carbonari@intel.com>,
	"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>
Subject: Re: Problems with EDAC coexisting with BIOS
Date: Wed, 3 May 2006 13:37:40 -0700	[thread overview]
Message-ID: <20060503203740.GA17515@hockin.org> (raw)
In-Reply-To: <4459119D.10905@buttersideup.com>

On Wed, May 03, 2006 at 09:25:01PM +0100, Tim Small wrote:
> existing BIOSs, but the EDAC module could reprogram the chipset 
> error-signalling registers, so that an ECC error no longer triggers an 

This is key, I think.

> SMI.  The BIOS SMI handler could then read the signalling registers, and 
> leave the ECC registers well alone if ECC errors are not set to generate 
> an SMI.

The fundamental problem with SMI is that we CAN'T know what it is doing.
I've seen systems which trigger SMI from a GPIO toggled by a clock.  I've
seen systems trigger SMI from a chipset-internal periodic timer.  I've
seen chipsets route NMI->SMI or even MCE->SMI.  If the BIOS is polling the
error status registers from a periodic SMI, we're GOING to lose data.

The big hammer - turn off SMI - is probably OK on some systems, but is not
a general solution.  More and more hardware workarounds and features are
SMI based.  There are some rather interesting things that can be done in
SMM, *iff* we could get the BIOS out of the way.

Tim (watching EDAC from time to time, quietly)

  reply	other threads:[~2006-05-03 20:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 14:15 Problems with EDAC coexisting with BIOS Ong, Soo Keong
2006-04-24 14:29 ` Alan Cox
2006-05-03 20:25   ` Tim Small
2006-05-03 20:37     ` thockin [this message]
2006-05-04  9:45       ` Tim Small
2006-05-03 21:44     ` Alan Cox
2006-05-04  9:02       ` Tim Small
  -- strict thread matches above, loose matches on Subject: below --
2006-05-04 16:44 David Peterson
2006-05-03 23:06 David Peterson
2006-05-03 22:22 Doug Thompson
2006-05-03 21:39 Doug Thompson
2006-05-03 20:49 Gross, Mark
2006-04-26  3:24 Gross, Mark
2006-04-26  3:19 Gross, Mark
2006-04-25 23:25 Gross, Mark
2006-04-26  2:19 ` Corey Minyard
2006-04-26  2:34 ` Randy.Dunlap
2006-04-26 18:26   ` mark gross
2006-04-26 18:38     ` Randy.Dunlap
2006-04-26 19:39       ` mark gross
2006-04-26 20:17         ` Randy.Dunlap
2006-04-25 21:24 Gross, Mark
2006-04-25 22:39 ` Corey Minyard
2006-04-25 20:22 Gross, Mark
2006-04-25 18:19 Gross, Mark
2006-04-25 19:55 ` Corey Minyard
2006-04-24 18:14 Gross, Mark
2006-04-24 15:57 Gross, Mark
2006-04-24 17:08 ` Eric W. Biederman
2006-04-24 17:49 ` Alan Cox
2006-04-24 14:32 Ong, Soo Keong
2006-04-24 13:59 Ong, Soo Keong
2006-04-24 14:13 ` Alan Cox
2006-04-23  1:44 Gross, Mark
2006-04-21 22:36 Doug Thompson
2006-04-21 22:20 Gross, Mark
2006-04-22 18:31 ` Tim Small
2006-04-21 21:42 Doug Thompson
2006-04-21 21:32 Gross, Mark
2006-04-21 20:57 Doug Thompson
2006-04-21 16:01 Gross, Mark
2006-04-21 21:13 ` Ingo Oeser
2006-04-24 13:19 ` Alan Cox
2006-04-24 17:38   ` Doug Thompson

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=20060503203740.GA17515@hockin.org \
    --to=thockin@hockin.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=soo.keong.ong@intel.com \
    --cc=steven.carbonari@intel.com \
    --cc=tim@buttersideup.com \
    --cc=zhenyu.z.wang@intel.com \
    /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