lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36ca99e90807050250u718fa277t2297d6436fd14c4e@mail.gmail.com>
Date:	Sat, 5 Jul 2008 11:50:26 +0200
From:	"Bert Wesarg" <bert.wesarg@...glemail.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	masbock@...ux.vnet.ibm.com, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [9/9] MCE: Use 64bit machine check code on 32bit

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ