6 Oct
2021
6 Oct
'21
1:23 p.m.
On Wed, Oct 06, 2021 at 02:06:26PM +0300, Peter Ujfalusi wrote:
Hi,
The aim of this series is to clean up, make it easier to interpret and less 'chatty' prints aimed for debugging errors.
For example currently the DSP/IPC dump is printed every time we have an IPC timeout and it is posible to lost the first and more indicative dump to find the rootcause.
You might want to look at tracepoints and/or trace_printk, apart from anything else they're very useful for flight recorder style applications since they're very low overhead and have comparitively speeaking lots of storage available.