From: Johannes Berg <johannes@sipsolutions.net>
To: Joe Perches <joe@perches.com>, Lubomir Rintel <lkundrak@v3.sk>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mac80211_hwsim: use dyndbg for debug messages
Date: Wed, 28 Jun 2017 17:03:57 +0200 [thread overview]
Message-ID: <1498662237.12531.7.camel@sipsolutions.net> (raw)
In-Reply-To: <1498657062.8633.1.camel@perches.com>
On Wed, 2017-06-28 at 06:37 -0700, Joe Perches wrote:
> On Wed, 2017-06-28 at 15:17 +0200, Lubomir Rintel wrote:
> > The mac80211_hwsim doesn't offer a way to disable the debugging
> > output.
> > Unfortunately, it's pretty chatty, dumping a lot of stuff into the
> > message
> > buffer.
> >
> > This patch changes it to use dyndbg for controlling the debug
> > output.
> > It's disabled by default, but can be enabled by a module parameter
> > (1),
> > at runtime (2) or persisted in modprobe.conf (3).
> >
> > (1) modprobe mac80211_hwsim dyndbg=+p
> > (2) echo "module mac80211_hwsim +p"
> > >/sys/kernel/debug/dynamic_debug/control
> > (3) echo "options mac80211_hwsim dyndbg=+p"
> > >>/etc/modprobe.d/my.conf
>
> I wonder about the value at all of the 2 forms:
>
> wiphy_dbg -> only with #define DEBUG or dynamic_debug
> wiphy_debug -> always emitted at KERN_DEBUG
>
> Is there any real value in wiphy_debug?
>
> Should it just be converted to
>
> #define wiphy_debug wiphy_dbg
I don't think it should, there are some messages that we'd probably
just have to give a higher priority if we did this.
johannes
next prev parent reply other threads:[~2017-06-28 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 13:17 [PATCH] mac80211_hwsim: use dyndbg for debug messages Lubomir Rintel
2017-06-28 13:37 ` Joe Perches
2017-06-28 15:03 ` Johannes Berg [this message]
2017-06-28 15:02 ` Johannes Berg
2017-06-28 19:10 ` Lubomir Rintel
2017-06-28 19:23 ` Joe Perches
2017-06-29 13:08 ` 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=1498662237.12531.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=joe@perches.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkundrak@v3.sk \
/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).