2009-06-15 02:25:27 -06:00
|
|
|
obj-y = mce.o
|
2007-10-23 14:37:23 -06:00
|
|
|
|
2009-05-27 13:56:54 -06:00
|
|
|
obj-$(CONFIG_X86_NEW_MCE) += mce-severity.o
|
x86, mce: use 64bit machine check code on 32bit
The 64bit machine check code is in many ways much better than
the 32bit machine check code: it is more specification compliant,
is cleaner, only has a single code base versus one per CPU,
has better infrastructure for recovery, has a cleaner way to communicate
with user space etc. etc.
Use the 64bit code for 32bit too.
This is the second attempt to do this. There was one a couple of years
ago to unify this code for 32bit and 64bit. Back then this ran into some
trouble with K7s and was reverted.
I believe this time the K7 problems (and some others) are addressed.
I went over the old handlers and was very careful to retain
all quirks.
But of course this needs a lot of testing on old systems. On newer
64bit capable systems I don't expect much problems because they have been
already tested with the 64bit kernel.
I made this a CONFIG for now that still allows to select the old
machine check code. This is mostly to make testing easier,
if someone runs into a problem we can ask them to try
with the CONFIG switched.
The new code is default y for more coverage.
Once there is confidence the 64bit code works well on older hardware
too the CONFIG_X86_OLD_MCE and the associated code can be easily
removed.
This causes a behaviour change for 32bit installations. They now
have to install the mcelog package to be able to log
corrected machine checks.
The 64bit machine check code only handles CPUs which support the
standard Intel machine check architecture described in the IA32 SDM.
The 32bit code has special support for some older CPUs which
have non standard machine check architectures, in particular
WinChip C3 and Intel P5. I made those a separate CONFIG option
and kept them for now. The WinChip variant could be probably
removed without too much pain, it doesn't really do anything
interesting. P5 is also disabled by default (like it
was before) because many motherboards have it miswired, but
according to Alan Cox a few embedded setups use that one.
Forward ported/heavily changed version of old patch, original patch
included review/fixes from Thomas Gleixner, Bert Wesarg.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-04-28 11:07:31 -06:00
|
|
|
obj-$(CONFIG_X86_OLD_MCE) += k7.o p4.o p6.o
|
|
|
|
|
obj-$(CONFIG_X86_ANCIENT_MCE) += winchip.o p5.o
|
2009-06-15 02:28:38 -06:00
|
|
|
obj-$(CONFIG_X86_MCE_INTEL) += mce_intel.o
|
|
|
|
|
obj-$(CONFIG_X86_MCE_AMD) += mce_amd.o
|
2007-10-23 14:37:23 -06:00
|
|
|
obj-$(CONFIG_X86_MCE_NONFATAL) += non-fatal.o
|
2009-02-12 05:49:31 -07:00
|
|
|
obj-$(CONFIG_X86_MCE_THRESHOLD) += threshold.o
|
2009-04-29 11:31:00 -06:00
|
|
|
obj-$(CONFIG_X86_MCE_INJECT) += mce-inject.o
|
2009-06-15 02:25:27 -06:00
|
|
|
|
2009-06-15 02:26:10 -06:00
|
|
|
obj-$(CONFIG_X86_THERMAL_VECTOR) += therm_throt.o
|
