> "Memory Error Section 2". One option we have without having to disturb > user space handler of memory error trace data would be to change > "struct cper_mem_err_compact" so the affected elements are of > __u32 instead of __u16. Drawback of this option is that the trace > buffer will be unnecessarily bigger if a platform generates > "Memory Error Section" data instead of "Memory Error Section 2" data. That structure is visible to user level consumers of the event (perhaps just one of those right now?): git://git.fedorahosted.org/rasdaemon.git We were not as smart as UEFI and didn't include a version number, or other plan, that would allow us to transition to a new format cleanly. Perhaps we could re-purpose some of the high order "validation_bits" as a version number? It's a u64 and UEFI 2.5 is only up to bit21 so far, so perhaps it will be a long, long time before they get that many fields in some future standard. -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
