public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mws@twisted-brains.org
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] dynamic printk - core infrastructure
Date: Tue, 01 Apr 2008 22:09:43 +0200	[thread overview]
Message-ID: <47F29687.3060403@twisted-brains.org> (raw)
In-Reply-To: <20080401194951.GC12029@redhat.com>

hi,

Jason Baron schrieb:
> Add the ability to dynamically enable/disable pr_debug()/dev_dbg() in the
> kernel. Yes, these calls could be converted to printk(KERN_DEBUG), but there
> are enough to cause overhead. Additionally, the logs become difficult to read.
> Here, one can turn on and off these messages per .c source file via:
> 
> echo "add file.c" > /sys/kernel/debug/dynamic_printk/files
> echo "remove file.c" > /sys/kernel/debug/dynamic_printk/files
> 
> There is also a special 'all' value that turns on all the debugging messages.
> 
> Signed-off-by: Jason Baron <jbaron@redhat.com>
> ---
> 
--snip --

> diff --git a/include/linux/device.h b/include/linux/device.h
> index db375be..b007f61 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -587,6 +587,17 @@ extern const char *dev_driver_string(struct device *dev);
>  #define dev_info(dev, format, arg...)		\
>  	dev_printk(KERN_INFO , dev , format , ## arg)
>  
> +#ifdef CONFIG_DYNAMIC_PRINTK
> +extern void dyanmic_printk(char *, char *, ...);

this external should be dynamic_printk (typo), shouldn't it?

regards
marcel




  reply	other threads:[~2008-04-01 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 19:49 [patch 1/3] dynamic printk - core infrastructure Jason Baron
2008-04-01 20:09 ` mws [this message]
2008-04-01 21:47 ` Randy Dunlap
2008-04-02  2:07   ` Joe Perches
2008-04-02 18:21     ` Jason Baron
2008-04-02 18:58       ` Joe Perches
2008-04-04 18:13         ` Jason Baron
2008-04-04 18:33           ` Joe Perches

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=47F29687.3060403@twisted-brains.org \
    --to=mws@twisted-brains.org \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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