From: Alexander Aring <alex.aring@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH] ieee802154: Add trace events for rdev->ops
Date: Fri, 17 Apr 2015 12:32:42 +0200 [thread overview]
Message-ID: <20150417103241.GC3288@omega> (raw)
In-Reply-To: <20150417100355.GA3288@omega>
On Fri, Apr 17, 2015 at 12:03:55PM +0200, Alexander Aring wrote:
> Hi,
>
> On Sun, Apr 12, 2015 at 02:07:33PM +0200, Guido Günther wrote:
> > This is based on the rdev->ops tracing code from net/wireless/.
> >
>
> this patch looks good. I tested it with trace-cmd:
>
> 1. trace-cmd record -e cfg802154:802154_rdev_set_pan_id
>
> 2. iwpan dev wpan0 set pan_id 0xbeaa
>
> 3. trace-cmd report
>
> result:
>
> version = 6
> cpus=1
> iwpan-1266 [000] 892.921639: 802154_rdev_set_pan_id: phy0, wpan_dev(1), pan id: 0xbeaa
>
> also test it with channel and it works pretty well. (I am not a
> trace-cmd export at the moment, my previous use-case was enough to use
> the raw ftrace interface).
>
>
> I looked again for the byteorder handling and detected that trace-cmd has
> a cfg802154 plugin [0]. It looks like the plugin is there, to doing
s/cfg802154/cfg80211/
> byteorder translation in userspace instead kernelspace.
>
> Looking into "__le16_to_cpup" stuff in wireless trace.h show something
> like [1].
>
> Do you think we can do this in the same way? Then we need some
> plugin_cfg802154 in trace-cmd tool.
>
Please read the other mail which I also mark an issue and we should move
the byteorder translation into the format string argument. I suppose, what
wireless do with the cfg80211 plugin is to printout the handling of function
__le16_to_cpup (in our case __le16_to_cpu) more correct. So we need
both, translation byteorder in kernelspace (for the __le16 parameter)
and (to show the __le16_to_cpu in userspace correct).
- Alex
next prev parent reply other threads:[~2015-04-17 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 12:07 [PATCH] ieee802154: Add trace events for rdev->ops Guido Günther
2015-04-17 10:03 ` Alexander Aring
2015-04-17 10:32 ` Alexander Aring [this message]
2015-04-17 10:27 ` Alexander Aring
2015-04-20 18:36 ` Guido Günther
2015-04-17 11:49 ` Varka Bhadram
2015-04-20 18:35 ` Guido Günther
2015-04-20 18:50 ` Alexander Aring
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=20150417103241.GC3288@omega \
--to=alex.aring@gmail.com \
--cc=agx@sigxcpu.org \
--cc=linux-wpan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.