Re: [PATCH] x86: mce: Xeon75xx specific interface to get corrected memory error information v2

From: Andi Kleen
Date: Mon Mar 29 2010 - 03:47:26 EST


Andi Kleen <andi@xxxxxxxxxxxxxx> writes:

> x86: mce: Xeon75xx specific interface to get corrected memory error information v2

Ping? Please review this patch. Thanks.
-Andi

>
> [This version addresses the previous comments. It does not change
> any interface to the outside and does not attempt to encode DIMMs
> or anything like that, but only passes out the physical address of u
> a corrected error in the standard ADDR register field.
> So for the outside it looks exactly the same as if the CPU supported this
> natively, but no otherwise special interfaces.
>
> I hope this addresses previous concerns. I guess the DIMM error reporting
> can be revisited once there's a new reporting interface. There are still
> some traces of DIMM parsing in there, but it's only used for debug
> purposes now.]
>
> ---
>
> Xeon 75xx doesn't log physical addresses on corrected machine check
> events in the standard architectural MSRs. Instead the address has to
> be retrieved in a model specific way. This makes it impossible
> to do predictive failure analysis.

--
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/