lkml.org 
[lkml]   [2010]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] x86: mce: Xeon75xx specific interface to get corrected memory error information v2
From
Date
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> writes:

> I have some questions: Is it impossible to get the address
> after polling handler have processed? e.g. Is it possible to
> implement this module as mcelog's add-on that hooked & invoked
> immediately after reading /dev/mcelog? I guess there are
> some limitation/restriction to call pfa_command().

You need to be in ring 0. In theory you could do it later, but then
you risk losing the address if there is another error.

> Are there any alternative way to get the address?

No.

> Polling like edac_i7 doesn't help this?

No.

>
> You pointed "This makes it impossible to do predictive failure
> analysis", but I guess we could do rough-but-enough analysis that
> requires coarse resolution like sockets. Or we should not expect

The main predictive failure analysis interesting here is bad page
offlining and for that you need an address.

-Andi

--
ak@linux.intel.com -- Speaking for myself only.


\
 
 \ /
  Last update: 2010-03-29 12:57    [W:0.042 / U:0.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site