From: Greg KH <gregkh@linuxfoundation.org>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Joe Perches <joe@perches.com>,
Xenia Ragiadakou <burzalodowa@gmail.com>,
Jason Baron <jbaron@akamai.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Dynamic debug on by default?
Date: Wed, 14 Aug 2013 11:02:00 -0700 [thread overview]
Message-ID: <20130814180200.GA16963@kroah.com> (raw)
In-Reply-To: <20130814172043.GB22934@xanatos>
On Wed, Aug 14, 2013 at 10:20:43AM -0700, Sarah Sharp wrote:
> On Wed, Aug 14, 2013 at 10:04:10AM -0700, Greg KH wrote:
> > On Wed, Aug 14, 2013 at 09:51:54AM -0700, Joe Perches wrote:
> > > On Wed, 2013-08-14 at 09:40 -0700, Sarah Sharp wrote:
> > > > Hi Xenia,
> > > >
> > > > I'm a bit confused. I thought that debugging messages would be turned
> > > > off by default for a module if CONFIG_DYNAMIC_DEBUG was turned on. When
> > > > I tested your patch to remove the CONFIG_USB_XHCI_HCD_DEBUGGING and just
> > > > use dev_dbg, the messages from the xHCI driver appeared in dmesg by
> > > > default.
> > > >
> > > > That generates a lot of log spew. We can have distros add a boot
> > > > parameter option to turn off debug messages, but that boot parameter is
> > > > limited to 1023 characters. I'm concerned that if more drivers add
> > > > dynamic debugging, the distros will eventually run out of space in the
> > > > dynamic debugging boot parameter. I know Greg was ripping out debugging
> > > > config options in other USB drivers, so this is a bit concerning.
> > > >
> > > > Jason, is there a way within the xHCI driver to say that dynamic
> > > > debugging should be off by default? I've looked through the
> > > > documentation, and I can't find anything like that documented.
> > >
> > > #undefine DEBUG
> > >
> > > > I've attached my .config file, in case I have something misconfigured.
> > >
> > > Because of:
> > >
> > > drivers/usb/host/Makefile:ccflags-$(CONFIG_USB_DEBUG) := -DDEBUG
> >
> > Yes, that's the problem, I'm trying to get rid of the CONFIG_USB_DEBUG
> > flag, and I'm almost there. There are some host controllers that still
> > use it for some things that I have not cleaned up fully yet.
>
> Do you think those patches will land in 3.12? If not, I'll add an
> #undefine DEBUG to xhci.h to avoid the log spew.
Don't undefine it, if a user sets CONFIG_USB_DEBUG they obviously want
to see that spew :)
As for when it can be removed, no, it's probably not going to make 3.12,
although a lot of the work is already done and in my usb-next tree.
There are still a number of places where this is still used in the host
controller drivers that I haven't cleaned up yet:
~/linux/work/usb/drivers/usb/host $ git grep -w "ifdef DEBUG" | wc -l
37
~/linux/work/usb/drivers/usb/host $ git grep -wl "ifdef DEBUG"
ehci-fsl.c
ehci-hcd.c
ehci-q.c
ehci.h
fotg210-hcd.c
fotg210.h
fusbh200-hcd.c
fusbh200.h
imx21-hcd.c
imx21-hcd.h
ohci-dbg.c
ohci-hcd.c
ohci-spear.c
ohci.h
oxu210hp-hcd.c
uhci-debug.c
uhci-hcd.c
The hardest ones will be ohci and ehci, as there are different code
paths for when debugging is enabled (the debug stats generation and
dumping).
I'm swamped with "real work" at the moment and will not get to these
anytime soon, but if someone else wants to pick up the work and run with
it, I would love to see it done.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-14 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 16:40 Dynamic debug on by default? Sarah Sharp
2013-08-14 16:51 ` Joe Perches
2013-08-14 17:04 ` Greg KH
2013-08-14 17:20 ` Sarah Sharp
2013-08-14 18:02 ` Greg KH [this message]
2013-08-14 18:21 ` Jason Baron
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=20130814180200.GA16963@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=burzalodowa@gmail.com \
--cc=jbaron@akamai.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
/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