On 2013/10/11 02:32AM, Chen Gong wrote: > Use trace interface to elaborate all H/W error related > information. > > Signed-off-by: Chen, Gong <gong.chen@xxxxxxxxxxxxxxx> > --- <snip> > +TRACE_EVENT(extlog_mem_event, > + TP_PROTO(u32 etype, > + char *dimm_loc, > + const uuid_le *fru_id, > + char *fru_text, > + u64 error_count, > + u32 severity, > + u64 phy_addr, > + char *mem_loc), [Adding Mauro...] This looks very similar to the trace event I wrote a while back, which was similar to the one provided by ghes_edac: http://thread.gmane.org/gmane.linux.kernel.pci/24616 Seems to me this has the same issues we previously discussed w.r.t EDAC conflicts... Regards, Naveen -- 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
