From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org,
Mordechay Goodstein <mordechay.goodstein@intel.com>
Subject: Re: [PATCH 07/11] iwlwifi: add skb address to tx cmd in trace events data
Date: Wed, 20 Dec 2017 18:22:34 +0200 [thread overview]
Message-ID: <87wp1he5dh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1513786686.4827.485.camel@coelho.fi> (Luca Coelho's message of "Wed, 20 Dec 2017 18:18:06 +0200")
Luca Coelho <luca@coelho.fi> writes:
> On Wed, 2017-12-20 at 17:49 +0200, Kalle Valo wrote:
>> Luca Coelho <luca@coelho.fi> writes:
>>
>> > From: Mordechay Goodstein <mordechay.goodstein@intel.com>
>> >
>> > This helps matching tx cmd with other trace events, like
>> > net_dev_xmit
>> > and net_dev_queue etc.
>> >
>> > Signed-off-by: Mordechay Goodstein <mordechay.goodstein@intel.com>
>> > Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
>>
>> [...]
>>
>> > @@ -120,9 +121,9 @@ TRACE_EVENT(iwlwifi_dev_tx,
>> > __get_dynamic_array(buf1),
>> > skb->len - hdr_len);
>> > ),
>> > - TP_printk("[%s] TX %.2x (%zu bytes)",
>> > + TP_printk("[%s] TX %.2x (%zu bytes) skbaddr=%p",
>> > __get_str(dev), ((u8
>> > *)__get_dynamic_array(buf0))[0],
>> > - __entry->framelen)
>> > + __entry->framelen, __entry->skbaddr)
>> > );
>>
>> Just so that you know there has been a lot of changes recently about
>> %p,
>> I think the addresses are nowadays hashed due to security reasons. No
>> idea if it afffects tracing events, but just wanted to point out
>> this.
>
> Yeah, I've seen some discussions and I even commented that in our
> internal review. But I reckoned that if they are all hash, it should
> still be possible to match them.
Good point, matching is of course possible with hashes.
> It would be good to check if that's done also for traces...
Yeah, please let me know if you find out that.
--
Kalle Valo
next prev parent reply other threads:[~2017-12-20 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 12:38 [PATCH 00/11] iwlwifi: updates intended for v4.16 2017-12-18 Luca Coelho
2017-12-18 12:38 ` [PATCH 01/11] iwlwifi: support internal debug data collection for new devices Luca Coelho
2017-12-18 12:38 ` [PATCH 02/11] iwlwifi: avoid duplicate sw reset executions in the code Luca Coelho
2017-12-18 12:38 ` [PATCH 03/11] iwlwifi: mvm: force quota update upon NoA setting Luca Coelho
2017-12-18 12:38 ` [PATCH 04/11] iwlwifi: runtime: sync FW and host clocks for logs Luca Coelho
2017-12-18 12:38 ` [PATCH 05/11] iwlwifi: mvm: support RX flags API change Luca Coelho
2017-12-18 12:38 ` [PATCH 06/11] iwlwifi: fw: fix the enums in the rate scaling API Luca Coelho
2017-12-18 12:38 ` [PATCH 07/11] iwlwifi: add skb address to tx cmd in trace events data Luca Coelho
2017-12-20 15:49 ` Kalle Valo
2017-12-20 16:18 ` Luca Coelho
2017-12-20 16:22 ` Kalle Valo [this message]
2017-12-21 11:00 ` Luca Coelho
2017-12-18 12:38 ` [PATCH 08/11] iwlwifi: mvm: don't warn on multiple packets when opening a queue Luca Coelho
2017-12-18 12:38 ` [PATCH 09/11] iwlwifi: mvm: adjust to quota offload Luca Coelho
2017-12-18 12:38 ` [PATCH 10/11] iwlwifi: mvm: send the low latency command Luca Coelho
2017-12-18 12:38 ` [PATCH 11/11] iwlwifi: define and use if iwl_mvm_has_tlc_offload Luca Coelho
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=87wp1he5dh.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=mordechay.goodstein@intel.com \
/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).