From: Jason Baron <jbaron@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [patch 0/3] dynamic printk
Date: Tue, 1 Apr 2008 15:48:36 -0400 [thread overview]
Message-ID: <20080401194836.GB12029@redhat.com> (raw)
hi,
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.
I hope that these patches are useful for people writing new kernel code, for
system debugging and testing. In enabling the 'all' feature on the kernel I was
running i got a bunch of messages... (i'm not sure what they mean, but they
could point out an error or a kernel optimization that could be made, which I
didn't necessarily know about otherwise).
thanks,
-Jason
Apr 1 10:33:38 dhcp83-106 kernel: Already setup manip DST for ct ffff81007d800140
Apr 1 10:33:38 dhcp83-106 kernel: Already setup manip SRC for ct ffff81007d800140
Apr 1 10:33:38 dhcp83-106 kernel: Already setup manip DST for ct ffff81007d800a00
Apr 1 10:33:38 dhcp83-106 kernel: Already setup manip SRC for ct ffff81007d800a00
Apr 1 10:33:39 dhcp83-106 kernel: Already setup manip DST for ct ffff81007d800a00
Apr 1 10:33:39 dhcp83-106 kernel: Already setup manip SRC for ct ffff81007d800a00
Apr 1 10:33:39 dhcp83-106 kernel: Already setup manip DST for ct ffff81007d800a00
Apr 1 10:33:39 dhcp83-106 kernel: Already setup manip SRC for ct ffff81007d800a00
Apr 1 10:33:40 dhcp83-106 kernel: Already setup manip DST for ct ffff810071851dc0
Apr 1 10:33:40 dhcp83-106 kernel: Already setup manip SRC for ct ffff810071851dc0
Apr 1 10:33:40 dhcp83-106 kernel: Already setup manip DST for ct ffff81007d800a00
Apr 1 10:33:40 dhcp83-106 kernel: Already setup manip SRC for ct ffff81007d800a00
reply other threads:[~2008-04-01 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080401194836.GB12029@redhat.com \
--to=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
all inboxes | Powered by JetHome®