From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] ath10k: Add debugging for tx-credits usage.
Date: Mon, 24 Mar 2014 09:58:55 -0700 [thread overview]
Message-ID: <5330644F.5050906@candelatech.com> (raw)
In-Reply-To: <871txr7svw.fsf@kamboji.qca.qualcomm.com>
On 03/24/2014 04:12 AM, Kalle Valo wrote:
> greearb@candelatech.com writes:
>
>> From: Ben Greear <greearb@candelatech.com>
>>
>> This helps track tx credits accounting and usage. If
>> firmware hangs or otherwise fails to return credits, one
>> can more easily see the last few command types that
>> was send to the firmware.
>>
>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>
> This patchset didn't apply, and the sha1 ids were useless so that 3-way
> merge didn't work. Can you rebase, please? And better yet if you rebase
> in top of my master branch.
I will do this. I must have some conflicting patch between your top of
tree and this patch in my tree...
>> - status = ath10k_htc_send(htc, ATH10K_HTC_EP_0, skb);
>> + status = ath10k_htc_send(htc, ATH10K_HTC_EP_0, skb, __LINE__);
>
> Using line numbers in debug messages is very cumbersome. Some people
> cherry pick patches, have their own changes and whatnot which will make
> it more difficult to read the debug logs. Isn't there any better way to
> do this?
It is nasty, but I wanted to keep performance overhead light.
I could do an enum instead if you think that would be an improvement.
>> --- a/drivers/net/wireless/ath/ath10k/wmi.c
>> +++ b/drivers/net/wireless/ath/ath10k/wmi.c
>> @@ -544,7 +544,7 @@ static int ath10k_wmi_cmd_send_nowait(struct ath10k *ar, struct sk_buff *skb,
>> cmd_hdr->cmd_id = __cpu_to_le32(cmd);
>>
>> memset(skb_cb, 0, sizeof(*skb_cb));
>> - ret = ath10k_htc_send(&ar->htc, ar->wmi.eid, skb);
>> + ret = ath10k_htc_send(&ar->htc, ar->wmi.eid, skb, 0x71100000 | cmd_id);
>> trace_ath10k_wmi_cmd(cmd_id, skb->data, skb->len, ret);
>
> What does 0x71100000 stand for?
It's just something that is easily grepped for, and is obviously not
a line number.
Hopefully someone will have a better idea how to do this sort of thing,
as my patch is pretty far down the slope towards total hack :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2014-03-24 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 18:55 [PATCH 1/3] ath10k: Add debugging for tx-credits usage greearb
2014-03-21 18:55 ` [PATCH 2/3] ath10k: Better firmware loading error messages greearb
2014-03-24 11:21 ` Kalle Valo
2014-03-21 18:55 ` [PATCH 3/3] ath10k: add otp and firmware boot " greearb
2014-03-24 11:25 ` Kalle Valo
2014-03-24 11:12 ` [PATCH 1/3] ath10k: Add debugging for tx-credits usage Kalle Valo
2014-03-24 11:21 ` Michal Kazior
2014-03-24 16:50 ` Ben Greear
2014-03-25 7:27 ` Michal Kazior
2014-03-25 15:14 ` Ben Greear
2014-03-26 7:18 ` Michal Kazior
2014-03-26 14:40 ` Ben Greear
2014-03-26 19:41 ` Janusz Dziedzic
2014-03-24 16:58 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5330644F.5050906@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).