Re: Boot-time dynamic debugging?

From: Thomas Renninger
Date: Mon Aug 02 2010 - 10:11:13 EST

On Monday 02 August 2010 15:53:24 Pekka Enberg wrote:
> > On Sun, Aug 01, 2010 at 03:10:40PM +0300, Pekka Enberg wrote:
> >> Commit 346e15beb5343c2eb8216d820f2ed8f150822b08 ("driver core: basic
> >> infrastructure for per-module dynamic debug messages") removed
> >> "dynamic_printk" kernel parameter from the dynamic debugging subsystem
> >> (and forgot to update Documentation/kernel-parameters.txt). How can I
> >> use the new subsystem for enabling boot-time dev_dbg() calls for
> >> non-modular kernels?
> On Mon, Aug 2, 2010 at 4:47 PM, Jason Baron <jbaron@xxxxxxxxxx> wrote:
> > Right now, you can not enable them dynamically from the boot command
> > line (only via the debugfs file). However, Thomas Renninger, has posted
> > a series to add back the boot-time functionality, see:
> >
> > Subject: [patch 0/3] Dynamic Debug providing early boot debug messages via
> > boot parameter
> >
> >
> > So I intend to queue those up for 2.6.36, and also update the
> > documentation.
> Oh, great!
> Acked-by: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
> Btw, can you easily enable all dev_dbg() calls with the boot parameter?
I expect yes, but never explicitly tried it, dev_dbg should result in
printk(KERN_DEBUG ...) after some macro/inline func processing.

Be aware that I sent another neat ddebug functionality:
Subject on LKML: [PATCH] Dynamic Debug: Introduce global fake module param module.ddebug

If, take the second post (same mail thread) which is the same patch
with some documentation added.
It's based on top of the patchseries mentioned above.
Would be great if someone could pick it up as well.
I was not sure about the fact that drivers must not use ddebug as parameter
anymore with this patch and how to document that, quick review and/or
comments appreciated.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at