On 08/12/2013 11:26 PM, Borislav Petkov wrote:
On Mon, Aug 12, 2013 at 02:25:57PM -0300, Mauro Carvalho Chehab wrote:
Userspace still needs the EDAC sysfs, in order to identify how the
memory is organized, and do the proper memory labels association.
What edac_ghes does is to fill those sysfs nodes, and to call the
existing tracing to report errors.
I suppose you're referring to the entries under /sys/devices/system/edac/mc?
I'm not sure I understand how this helps. ghes_edac seems to just be
populating this based on dmi, which if I'm not mistaken, can be obtained
in userspace (mcelog as an example).
Also, on my system, all DIMMs are being reported under mc0. I doubt if
the labels there are accurate.
This is the only reason which justifies EDAC's existence. Naveen, can
your BIOS directly report the silkscreen label of the DIMM in error?
Generally, can any BIOS do that?
More specifically, what are those gdata_fru_id and gdata_fru_text
things?
My understanding was that this provides the DIMM serial number, but I'm
double checking just to be sure.
Thanks,
Naveen
Because if it can, then having the memory error tracepoint come direct
from APEI should be enough. The ghes_edac functionality could be then
fallback for BIOSes which cannot report the silkscreen label and in such
case I can imagine keeping both tracepoints, but disabling one of the
two...
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
