[alsa-devel] [PATCH] ALSA: get rid of CONFIG_SND_VERBOSE_PRINTK

Alan Stern stern at rowland.harvard.edu
Thu Jun 6 22:42:41 CEST 2013

On Tue, 4 Jun 2013, Joe Perches wrote:

> On Tue, 2013-06-04 at 16:54 -0400, Alan Stern wrote:
> > I don't see how DEFAULT_DEBUG_LEVEL can be used to optimize away
> > anything.  The user can always change the value of the "debug" module
> > parameter while the system is running.  The only valid opportunity for
> > optimization would be if CONFIG_SND_DEBUG was disabled; then all these 
> > messages would disappear.
> Not really.
> Think of CONFIG_SND_DEBUG as a level. (0, 1, 2)
> or maybe think of it as CONFIG_SND_DEBUG_VERBOSITY.
> There could still be ability to have CONFIG_SND_DEBUG
> limit the compiled-in messages to those below the
> #define value and still then have runtime control over
> which ones are displayed.

How useful really is it to be able to limit the amount of debugging
messages at runtime?  Does anybody ever actually adjust the "debug"  
module parameter?

In my opinion, this is not worth the extra space required.  Virtually 
all the benefit of different debugging levels can be obtained by 
defining different symbols at compile time, such as CONFIG_SND_DEBUG 
and CONFIG_SND_VERBOSE_DEBUG.  That gives you two levels of debugging 
(not counting the "none" setting), which is enough for everything but 
snd_printddd().  Does anybody really need a third level?

Alan Stern

More information about the Alsa-devel mailing list