Messages in this thread | | | From | "Luck, Tony" <> | Subject | RE: [PATCH 3/3] mce: acpi/apei: trace: Enable ghes memory error trace event | Date | Tue, 13 Aug 2013 17:39:00 +0000 |
| |
> In the meantime, like Boris suggests, I think we can have a different > trace event for raw APEI reports - userspace can use it as it pleases. > > Once ghes_edac gets better, users can decide whether they want raw APEI > reports or the EDAC-processed version and choose one or the other trace > event.
It's cheap to add as many tracepoints as we like - but may be costly to maintain. Especially if we have to tinker with them later to adjust which things are logged, that puts a burden on user-space tools to be updated to adapt to the changing API.
Mauro has written his user-space tool to process the ghes-edac events: git://git.fedorahosted.org/rasdaemon.git
Who is writing the user space tools to process the new apei tracepoints you want to add?
I'm not opposed to these patches - just wondering who is taking the next step to make them useful.
-Tony
| |