public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Paul Gortmaker <p_gortmaker@yahoo.com>
Cc: marcelo@conectiva.com.br, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bluesmoke/MCE support optional
Date: Thu, 28 Feb 2002 18:47:10 -0800	[thread overview]
Message-ID: <20020301024710.GF2711@matchmail.com> (raw)
In-Reply-To: <3C7E465A.4B3F4D9@yahoo.com>
In-Reply-To: <3C7E465A.4B3F4D9@yahoo.com>

On Thu, Feb 28, 2002 at 10:01:46AM -0500, Paul Gortmaker wrote:
> 
> Meant to do this a while ago.  Could do it via adding "nosmoke.c"  :-)
> (similar to fs/noquot.c) instead of #ifdef in bluesmoke.c, if somebody
> had a strong preference one way or the other.
> 
> Patch is against 2.4.18, complete with Aunt Tillie(tm) help text, etc.
> 
> Paul.
> 
> 
> --- Documentation/Configure.help~	Sat Feb  2 06:50:31 2002
> +++ Documentation/Configure.help	Thu Feb 28 09:01:28 2002
> @@ -17450,6 +17450,17 @@
>    The module is called shwdt.o. If you want to compile it as a module,
>    say M here and read Documentation/modules.txt.
>  	      
> +Machine Check Exception
> +CONFIG_X86_MCE
> +  Machine Check Exception support allows the processor to notify the
> +  kernel if it detects a problem (e.g. overheating, component failure).
> +  The action the kernel takes depends on the severity of the problem, 
> +  ranging from a warning message on the console, to halting the machine.
> +  Your processor must be a Pentium or newer to support this - check the 
> +  flags in /proc/cpuinfo for mce.  Note that some older Pentium systems
> +  have a design flaw which leads to false MCE events - for these and
> +  old non-MCE processors (386, 486), say N.  Otherwise say Y.
> +

This should be tied to the processor type options...

  parent reply	other threads:[~2002-03-01  2:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 15:01 [PATCH] bluesmoke/MCE support optional Paul Gortmaker
2002-03-01  0:11 ` Alan Cox
2002-03-01  7:18   ` Paul Gortmaker
2002-03-01 11:51     ` Alan Cox
2002-03-01  9:56   ` Dave Jones
2002-03-01  2:47 ` Mike Fedyk [this message]
2002-03-01 12:31   ` Alan Cox
2002-03-01 12:55     ` Dave Jones
2002-03-03 10:57       ` Paul Gortmaker
2002-03-03 13:53         ` Alan Cox
2002-03-01 15:10     ` Marcelo Tosatti
2002-03-01 17:29       ` Alan Cox

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=20020301024710.GF2711@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=p_gortmaker@yahoo.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