public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Tilman Schmidt <t.schmidt@phoenixsoftware.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dynamic_printk documentation
Date: Tue, 23 Dec 2008 11:22:29 -0500	[thread overview]
Message-ID: <20081223162229.GB4126@redhat.com> (raw)
In-Reply-To: <4950D8B5.5040404@phoenixsoftware.de>

On Tue, Dec 23, 2008 at 01:25:25PM +0100, Tilman Schmidt wrote:
> Where is the current debugfs interface to dynamic_printk documented?
> From the source in lib/dynamic_printk.c I deduced that
> 
> echo "set enable=1 <module_name>" > /sys/kernel/debug/dynamic_printk/modules
> 
> should enable debug output for module <module_name>, and verified
> experimentally that this does indeed work. Is that already described
> somewhere I just overlooked? If not, I would propose creating a file
> Documentation/dynamic_printk.txt.
> 
> Thanks,
> Tilman

hi,

Most of it is with the config parameter definition in lib/Kconfig.debug
(copied below). I can propose copying it into Documentation/ if you think it'd 
be useful.

thanks,

-Jason


config DYNAMIC_PRINTK_DEBUG
	bool "Enable dynamic printk() call support"
	default n
	depends on PRINTK
	select PRINTK_DEBUG
	help

	  Compiles debug level messages into the kernel, which would not
	  otherwise be available at runtime. These messages can then be
	  enabled/disabled on a per module basis. This mechanism implicitly
	  enables all pr_debug() and dev_dbg() calls. The impact of this
	  compile option is a larger kernel text size of about 2%.

	  Usage:

	  Dynamic debugging is controlled by the debugfs file,
	  dynamic_printk/modules. This file contains a list of the modules that
	  can be enabled. The format of the file is the module name, followed
	  by a set of flags that can be enabled. The first flag is always the
	  'enabled' flag. For example:

		<module_name> <enabled=0/1>
				.
				.
				.

	  <module_name> : Name of the module in which the debug call resides
	  <enabled=0/1> : whether the messages are enabled or not

	  From a live system:

		snd_hda_intel enabled=0
		fixup enabled=0
		driver enabled=0

	  Enable a module:

	  	$echo "set enabled=1 <module_name>" > dynamic_printk/modules

	  Disable a module:

	  	$echo "set enabled=0 <module_name>" > dynamic_printk/modules

	  Enable all modules:

		$echo "set enabled=1 all" > dynamic_printk/modules

	  Disable all modules:

		$echo "set enabled=0 all" > dynamic_printk/modules

	  Finally, passing "dynamic_printk" at the command line enables
	  debugging for all modules. This mode can be turned off via the above
	  disable command.


  reply	other threads:[~2008-12-23 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23 12:25 dynamic_printk documentation Tilman Schmidt
2008-12-23 16:22 ` Jason Baron [this message]
2009-01-03 18:48   ` Michael Kerrisk

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=20081223162229.GB4126@redhat.com \
    --to=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.schmidt@phoenixsoftware.de \
    /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