From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>,
David Miller <davem@davemloft.net>
Cc: Jim Cromie <jim.cromie@gmail.com>,
Jason Baron <jbaron@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: dynamic debug
Date: Fri, 22 Jun 2012 07:26:17 -0700 [thread overview]
Message-ID: <1340375177.31821.7.camel@joe2Laptop> (raw)
In-Reply-To: <1340367797.4491.21.camel@jlt3.sipsolutions.net>
On Fri, 2012-06-22 at 14:23 +0200, Johannes Berg wrote:
> Joe, Jim, Jason,
>
> Joe's conversion of mac80211 to pr_debug() was pretty much a disaster,
First I've heard of it.
> now people have to first select what they want in Kconfig, and then
> still enable dynamic debug in debugfs...
This doesn't parse for me.
Please illustrate further.
> That doesn't make any sense at
> all, and requires teaching everybody new tricks, so I'm basically
> reverting it for now in favour of pr_info() instead of pr_debug().
Why not just add #define DEBUG?
> I'd actually not mind using pr_debug() if it meant we could get rid of
> all the Kconfig symbols, but that's not possible.
>
> The biggest problem here really is that the dynamic debug infrastructure
> lets us enable messages at runtime, which is great, but the granularity
> is useless since you only have these possibilities:
What I think dyn_debug needs is a mask/level control.
so you can do the equivalent of
echo val > /somewhere
to control the tested against value
see: https://lkml.org/lkml/2011/8/21/128
next prev parent reply other threads:[~2012-06-22 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 12:23 dynamic debug Johannes Berg
2012-06-22 14:26 ` Joe Perches [this message]
2012-06-22 14:34 ` Johannes Berg
2012-06-22 14:41 ` Joe Perches
2012-06-22 14:48 ` Johannes Berg
2012-06-22 15:21 ` Johannes Berg
2012-06-22 15:32 ` Joe Perches
2012-06-22 15:36 ` Johannes Berg
2012-06-22 17:30 ` Johannes Berg
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=1340375177.31821.7.camel@joe2Laptop \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--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