On Wed, Aug 14, 2013 at 04:17:26PM +0530, Naveen N. Rao wrote:

- One, the logging format for APEI data is a bit verbose and hard
to parse. But, I suppose we could work with this if we make a few
changes. Is it ok to change how the APEI data is made available
through mc_event->driver_detail?

How?

- Two, if ghes_edac is enabled, it prevents other edac drivers
from being loaded. It looks like the assumption here is that if
ghes/firmware first is enabled, then *all* memory errors are reported
through ghes which is not true. We could have (a subset of) corrected
errors reported through ghes, some through CMCI and uncorrected errors
through MCE. So, if I'm not mistaken, if ghes_edac is enabled, we will
only receive ghes error events through mc_event and not the others.

The idea is to have a single tracepoint reporting memory errors. Where
you call it from shouldn't matter. Now, we have to make sure that we
don't report the same event more than once over different paths.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--