From: Joe Perches <joe@perches.com>
To: Jason Baron <jbaron@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, Jim Cromie <jim.cromie@gmail.com>
Subject: Re: [PATCH 4/6] mac80211: clean up debugging
Date: Mon, 25 Jun 2012 22:23:58 -0700 [thread overview]
Message-ID: <1340688238.3359.31.camel@joe2Laptop> (raw)
In-Reply-To: <20120625212904.GA9245@redhat.com>
On Mon, 2012-06-25 at 17:29 -0400, Jason Baron wrote:
> On Sun, Jun 24, 2012 at 11:30:58AM +0200, Johannes Berg wrote:
> > On Sat, 2012-06-23 at 08:40 -0700, Joe Perches wrote:
> >
> > > > FWIW, I would definitely prefer named rather than bitmap selectors :-)
> > >
> > > (Added Jason and Jim)
> > >
> > > Given it's a debug-only facility, I think bitmap
> > > selectors sufficient, Maybe adding an external
> > > utility to map names to bits would be enough to
> > > not need that feature in the kernel.
> >
> I've been thinking about that too - given that we can control each
> individual statement from userspace, perhaps most of the implementation
> for level/bitmap support could and should be done in userspace.
Maybe, but I think not. There are configs where DEBUG
is defined, dyn_debug is not used and debugging levels
are checked against a constant that allows various debug
tests to be compiled away completely.
I'd prefer to keep the control mechanism the same for
pr_debug uses with and without dynamic_debug.
Doing "echo foo > bar" is pretty simple and might be best
if was kept the same.
There does need to be a u32 for the mask/level and a bit
or 2 for determining if mask or level is used or nothing.
> > I think it would be good to use the jump_label mechanism to
> > implement it -- I do realise that still has runtime overhead for the
> > argument preparation, but still.
> >
> > Looking at the history, it seems that jump labels were at one point used
> > by reverted to fix gcc 3.3, I'm sure that could be resolved?
>
> Yes, there were some circular header dependencies issues - but they can
> be resolved. I will re-post this work.
I just did that here. What I've done is kind of messy
as I've moved a lot of kernel.h content around.
Hope yours is cleaner.
next prev parent reply other threads:[~2012-06-26 5:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 17:18 [PATCH v2 0/6] mac80211 debugging Johannes Berg
2012-06-22 17:18 ` [PATCH 1/6] mac80211: remove TKIP debug Johannes Berg
2012-06-22 17:18 ` [PATCH 2/6] mac80211: two small verbose debug cleanups Johannes Berg
2012-06-22 17:18 ` [PATCH 3/6] mac80211: pass sdata to some RX functions Johannes Berg
2012-06-22 17:18 ` [PATCH 4/6] mac80211: clean up debugging Johannes Berg
2012-06-23 8:02 ` Joe Perches
2012-06-23 13:04 ` Johannes Berg
2012-06-23 15:40 ` Joe Perches
2012-06-24 9:30 ` Johannes Berg
2012-06-25 21:29 ` Jason Baron
2012-06-26 5:23 ` Joe Perches [this message]
2012-06-23 16:03 ` Joe Perches
2012-06-22 17:18 ` [PATCH 5/6] mac80211: rename driver-trace file Johannes Berg
2012-06-22 17:18 ` [PATCH 6/6] mac80211: trace debug messages Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2012-06-22 13:14 mac80211 logging/tracing Johannes Berg
2012-06-22 13:14 ` [PATCH 4/6] mac80211: clean up debugging Johannes Berg
2012-06-22 14:37 ` Joe Perches
2012-06-22 14:43 ` Johannes Berg
2012-06-22 14:49 ` Joe Perches
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=1340688238.3359.31.camel@joe2Laptop \
--to=joe@perches.com \
--cc=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=johannes@sipsolutions.net \
--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).