mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: masbock@linux.vnet.ibm.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [9/9] MCE: Use 64bit machine check code on 32bit
Date: Sat, 5 Jul 2008 11:50:26 +0200	[thread overview]
Message-ID: <36ca99e90807050250u718fa277t2297d6436fd14c4e@mail.gmail.com> (raw)
In-Reply-To: <20080704212033.D40551B431F@basil.firstfloor.org>

Hi,

> Index: linux/arch/x86/Kconfig
> ===================================================================
> --- linux.orig/arch/x86/Kconfig
> +++ linux/arch/x86/Kconfig
> @@ -652,10 +652,37 @@ config X86_MCE
>          to disable it.  MCE support simply ignores non-MCE processors like
>          the 386 and 486, so nearly everyone can say Y here.
>
> +config X86_OLD_MCE
> +       depends on X86_32
> +       bool "Use legacy machine check code (will go away)"
> +       default n
> +       help
> +         Use the old i386 machine check code. This is merely intended for testing
> +         in a transition period. Try this if you run into any machine check
> +         related software problems.
> +         When in doubt say no.
> +
> +config X86_ANCIENT_MCE
> +       depends on X86_32
> +       bool "Support ancient machine check handler for very old CPUs"
> +       default n
> +       help
> +         Include support for family 5 (Intel Pentium 1 and Centaur Winchip)
> +         machine check code.  Machine check handles uncorrected CPU errors.
> +         Note that the P5 pentium support is disabled
> +         by default and can be only enabled on special hardware.
> +         The Winchip code doesn't do much.
> +         If you're still sure you want it, say n, otherwise n is safe
Is this first "n" a typo?

Bert

  reply	other threads:[~2008-07-05  9:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 21:20 [PATCH] [0/9] Use 64bit x86 machine check code for 32bit too Andi Kleen
2008-07-04 21:20 ` [PATCH] [1/9] MCE: Make 64bit mce code 32bit clean Andi Kleen
2008-07-04 21:20 ` [PATCH] [2/9] MCE: Implement the PPro bank 0 quirk in the 64bit machine check code Andi Kleen
2008-07-04 21:20 ` [PATCH] [3/9] MCE: Port K7 bank 0 quirk to 64bit mce code Andi Kleen
2008-07-04 21:20 ` [PATCH] [4/9] MCE: Call 64bit machine check through a call vector Andi Kleen
2008-07-04 21:20 ` [PATCH] [5/9] MCE: Rename mce_dont_init on 64bit to mce_disabled Andi Kleen
2008-07-04 21:20 ` [PATCH] [6/9] MCE: Provide exit_idle dummy functions for 32bit Andi Kleen
2008-07-04 21:20 ` [PATCH] [7/9] MCE: Remove machine check handler idle notify on 64bit Andi Kleen
2008-07-04 21:20 ` [PATCH] [8/9] MCE: Remove oops_begin() use in 64bit machine check Andi Kleen
2008-07-04 21:20 ` [PATCH] [9/9] MCE: Use 64bit machine check code on 32bit Andi Kleen
2008-07-05  9:50   ` Bert Wesarg [this message]
2008-07-05  9:54     ` Andi Kleen
2008-07-05 10:17       ` Bert Wesarg
2008-07-05 10:55         ` Andi Kleen
2008-07-10 18:23           ` Pavel Machek
2008-07-07 21:26 ` [PATCH] [0/9] Use 64bit x86 machine check code for 32bit too H. Peter Anvin
2008-07-07 21:37   ` H. Peter Anvin
2008-07-08  0:00     ` Max Asbock
2008-07-08  0:25       ` Andi Kleen
2008-07-07 22:09   ` Andi Kleen

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=36ca99e90807050250u718fa277t2297d6436fd14c4e@mail.gmail.com \
    --to=bert.wesarg@googlemail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masbock@linux.vnet.ibm.com \
    --cc=x86@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

Powered by JetHome