[PATCH] ath10k: add configurable debugging.

Kalle Valo kvalo at qca.qualcomm.com
Thu Jun 1 06:34:29 PDT 2017

Adrian Chadd <adrian at freebsd.org> writes:

>>>> --- a/drivers/net/wireless/ath/ath10k/core.c
>>>> +++ b/drivers/net/wireless/ath/ath10k/core.c
>>>> @@ -2444,6 +2444,8 @@ struct ath10k *ath10k_core_create(size_t
>>>> priv_size, struct device *dev,
>>>>      ar->hw_rev = hw_rev;
>>>>      ar->hif.ops = hif_ops;
>>>>      ar->hif.bus = bus;
>>>> +    ar->debug_mask = ath10k_debug_mask;
>>>> +    ar->trace_debug_mask = ath10k_debug_mask;
>>> Until now tracing has been always enabled, irrespective what debug_mask
>>> has contained. Now you are changing that and by default log messages are
>>> not delivered through tracing until user enables them. So I think to
>>> keep the old behaviour trace_debug_mask should be ATH10K_DBG_ANY
>>> (0xffffffff) by default and the user can modify the mask per device via
>>> the debugfs file.
>>> But is it really needed to be able to filter trace messages? debug_mask
>>> I understand, but not sure about trace_debug_mask.
>> FWIW, in brcmfmac I decided not to filter trace messages. The overhead
>> is relatively small and if needed you can pass filter expressions with
>> trace-cmd record.
> The reason for configuring it via a mask is that:
> * the previous behaviour is "always call debug(), conditionally print,
> always pass to trace"
> This meant that function arguments were evaluated even if things
> weren't being printed.
> So to avoid that in the default case, there are now two masks. If I
> have one mask then I can only trace what is being printed, which is
> not desired. I'd like to be able to have no overhead when doing no
> debugging, a little overhead when doing tracing (and only the items
> being traced), and then printing when I want to print.

Ok, so you want also filter tracing messages. Any particular reason for
that, limited storage space or something else? Just curious.

So what's the most expensive part here, the actual function call to
ath10k_dbg() or va_start()/ve_end() within the function? And do you have
before and after throughput numbers for this? And maybe also with
CONFIG_ATH10K_DEBUG is disabled, which should be the most fastest. It
would be good to know how much this has affect on performance.

We could of course always change ath10k_dbg()/ath10k_dbg_dump() to
inline functions (or maybe even cpp macros) but if va_start()/va_end()
are the expensive part that won't help.

Kalle Valo

More information about the ath10k mailing list