> Matt Fleming mentioned to me that Tony Luck recently fixed a > compatibility issue with Memory Error Record structure. > I ask, how do we want to handle the processing of a CPER > memory error record with support for larger DIMMs? I looked at this a bit when I was making the compatibility patch. The problem is how to take the larger value and report it to user space. We have all hard-coded field widths in the trace structure used that make this non-trivial at the moment. Supposedly there are changes coming to the perf infrastructure that will make it easier in the future to widen a field from u16 to u32. See http://lkml.org/lkml/2015/6/24/715 Maybe the future Steven described is here now, and someone can go in and fix the logging event and rasdaemon? -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
