[PATCH v2 0/3]

Florian Fainelli f.fainelli at gmail.com
Sat Aug 1 01:24:17 EDT 2020

On 7/31/2020 10:10 PM, Rakesh Pillai wrote:
>> -----Original Message-----
>> From: Florian Fainelli <f.fainelli at gmail.com>
>> Sent: Saturday, August 1, 2020 12:17 AM
>> To: Rakesh Pillai <pillair at codeaurora.org>; ath10k at lists.infradead.org
>> Cc: linux-wireless at vger.kernel.org; linux-kernel at vger.kernel.org;
>> kvalo at codeaurora.org; davem at davemloft.net; kuba at kernel.org;
>> netdev at vger.kernel.org
>> Subject: Re: [PATCH v2 0/3]
>> On 7/31/20 11:27 AM, Rakesh Pillai wrote:
>>> The history recording will be compiled only if
>>> ATH10K_DEBUG is enabled, and also enabled via
>>> the module parameter. Once the history recording
>>> is enabled via module parameter, it can be enabled
>>> or disabled runtime via debugfs.
>> Why not use trace prints and retrieving them via the function tracer?
>> This seems very ad-hoc.
> Tracing needs to be enabled to capture the events.
> But these events can be turned on in some kind of a debug build and capture the history to help us debug in case there is a crash.
> It wont even allocate memory if not enabled via module parameter.

I would suggest researching what other drivers do and also considering
the benefits, for someone doing system analysis of plugging into the
kernel's general tracing mechanism to have all information in the same
place and just do filtering on the record/report side.

More information about the ath10k mailing list