From: Nick Andrew <nick@nick-andrew.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Baron <jbaron@redhat.com>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [patch 0/3] dynamic_printk: new feature
Date: Thu, 1 May 2008 10:23:29 +1000 [thread overview]
Message-ID: <20080501002329.GD3914@tull.net> (raw)
In-Reply-To: <20080430124506.0dd2a473.akpm@linux-foundation.org>
On Wed, Apr 30, 2008 at 12:45:06PM -0700, Andrew Morton wrote:
> > Add the ability to dynamically enable/disable pr_debug()/dev_dbg() in the
> > kernel.
Yes, that's the kind of thing I've been thinking about adding myself.
> > echo "add module_name" > /sys/kernel/debug/dynamic_printk/modules
> > echo "remove module_name" > /sys/kernel/debug/dynamic_printk/modules
How about not just debug messages but setting a loglevel for each module
(and/or subsystem?); kernel messages emitted beneath the loglevel value
to be discarded.
> We're now in the situation where numerous different subsystems have
> implemented private mechnisms for tuning their printk verbosity levels.
And it grows over time; just in the last week a patch came through to
V4L ...
From: Andy Walls <awalls@radix.net>
Replace the unconditional printk() messages with printk() messages that are
enabled/disabled by a "debug" module parameter.
[...]
+#define dprintk(level, fmt, arg...)
> Have you considered the feasibility of ploddingly converting each of those
> drivers, one at a time over to the new infrastructure? Because that's what
> we should do, I'm afraid.
I can help with that.
Nick.
--
PGP Key ID = 0x418487E7 http://www.nick-andrew.net/
PGP Key fingerprint = B3ED 6894 8E49 1770 C24A 67E3 6266 6EB9 4184 87E7
prev parent reply other threads:[~2008-05-01 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 18:39 [patch 0/3] dynamic_printk: new feature Jason Baron
2008-04-30 19:45 ` Andrew Morton
2008-04-30 20:54 ` Joe Perches
2008-04-30 21:01 ` Jason Baron
2008-05-01 3:44 ` Greg KH
2008-05-01 0:23 ` Nick Andrew [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=20080501002329.GD3914@tull.net \
--to=nick@nick-andrew.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.