[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1498677816.8633.4.camel@perches.com>
Date: Wed, 28 Jun 2017 12:23:36 -0700
From: Joe Perches <joe@...ches.com>
To: Lubomir Rintel <lkundrak@...sk>,
Johannes Berg <johannes@...solutions.net>
Cc: Kalle Valo <kvalo@...eaurora.org>, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mac80211_hwsim: use dyndbg for debug messages
On Wed, 2017-06-28 at 21:10 +0200, Lubomir Rintel wrote:
> On Wed, 2017-06-28 at 17:02 +0200, Johannes Berg 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.
> >
> > Why is this a problem? It's pretty much a testing tool only, and much
> > of the point is to have message about it's internal state?
>
> I do use it as a development tool. I find it very convenient to always
> have a bunch of libvirt-managed LXC containers, some running hostapd
> instances with various access point configurations and some used for
> NetworkManager development and a mac80211_hwsim radio in each of them.
>
> An unfortunate side-effect is that my dmesg becomes next to useless due
> to the overwhelming amount of mac80211_hwsim logging.
Perhaps convert some of these to debugfs output?
Otherwise, many or most of these seem to be function
tracing type calls that could or should use ftrace.
Powered by blists - more mailing lists