On Fri, May 10, 2024 at 03:12:36PM -0700, Dan Williams wrote:
> I had asked Fabio to take a look at whether it made sense to continue
> with the concept of ras_userspace_consumers() especially since it seems
> limited to the EXTLOG case.
>
> In general I am finding that between OS Native and Firmware First error
> reporting the logging approaches are inconsistent.
>
> As far I can see rasdaemon would not even notice is the "daemon_active"
> debugfs file went away [1],
It tells the kernel that it is consuming the error info from the
tracepoints.
> and it should be the case that the tracepoints always fire whether
> daemon_active is open or not.
>
> So I was expecting this removal to be a conversation starter on the
> wider topic of error reporting consistency.
Yeah, and then they'll come and say: ew, we're getting error duplicates
- once logged in dmesg and once through the tracepoints.
So just like with the other thread, we have to figure out what our
scheme will be wrt hw error logging, agree on it and then make it
consistent.
Do we want to have both? Should it be configurable? Probably...
Anything else...?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
