From: Thomas Renninger <trenn@suse.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Jason Baron <jbaron@redhat.com>, Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
bjorn.helgaas@hp.com
Subject: Re: Boot-time dynamic debugging?
Date: Fri, 6 Aug 2010 16:03:53 +0200 [thread overview]
Message-ID: <201008061603.54058.trenn@suse.de> (raw)
In-Reply-To: <201008021614.00038.trenn@suse.de>
On Monday 02 August 2010 16:13:59 Thomas Renninger wrote:
> On Monday 02 August 2010 15:53:24 Pekka Enberg wrote:
...
> > 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.
My statement was wrong, from what I can see having a closer look:
printk(KERN_DEBUG...) messages will not show up, but dev_dbg will:
----------
asmlinkage int printk(const char * fmt, ...)
__attribute__ ((format (printf, 1, 2))) __cold;
static inline int printk(const char *s, ...)
__attribute__ ((format (printf, 1, 2)));
----------
I wonder whether the KERN_DEBUG can be differed at compile time
and could also result in a dynamic_pr_debug...
----------
#elif defined(CONFIG_DYNAMIC_DEBUG)
/* dynamic_pr_debug() uses pr_fmt() internally so we don't need it here */
#define pr_debug(fmt, ...) \
dynamic_pr_debug(fmt, ##__VA_ARGS__)
#elif defined(CONFIG_DYNAMIC_DEBUG)
#define dev_dbg(dev, format, ...) \
do { \
dynamic_dev_dbg(dev, format, ##__VA_ARGS__); \
}
----------
Thomas
prev parent reply other threads:[~2010-08-06 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 12:10 Boot-time dynamic debugging? Pekka Enberg
2010-08-02 13:47 ` Jason Baron
2010-08-02 13:53 ` Pekka Enberg
2010-08-02 14:13 ` Thomas Renninger
2010-08-06 14:03 ` Thomas Renninger [this message]
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=201008061603.54058.trenn@suse.de \
--to=trenn@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=gregkh@suse.de \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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