From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>,
Linux FS Devel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH 18/24] nilfs2: introduce superfluous debugging output option
Date: Mon, 17 Jun 2013 16:25:49 +0400 [thread overview]
Message-ID: <1371471949.2075.150.camel@slavad-ubuntu> (raw)
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Subject: [PATCH 18/24] nilfs2: introduce superfluous debugging output option
This patch adds CONFIG_NILFS2_DEBUG_SHOW_SPAM kernel
configuration option. This option enables output from
frequently called functions or detailed debugging output
from function's body.
Signed-off-by: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
CC: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
---
fs/nilfs2/Kconfig | 12 ++++++++++++
fs/nilfs2/debug.h | 22 +++++++++++++++++++++-
2 files changed, 33 insertions(+), 1 deletion(-)
diff --git a/fs/nilfs2/Kconfig b/fs/nilfs2/Kconfig
index c1ec3c9..39dc5c39 100644
--- a/fs/nilfs2/Kconfig
+++ b/fs/nilfs2/Kconfig
@@ -107,6 +107,18 @@ config NILFS2_DEBUG_BUFFER_MANAGEMENT
help
This option enables debugging output in page.c module.
+config NILFS2_DEBUG_SHOW_SPAM
+ bool "Enable superfluous debugging output"
+ default n
+ help
+ This option enables output from frequently called functions or
+ detailed debugging output from function's body. Please, be
+ cautious with enabling the option. Because it can be resulted
+ in huge amount of debugging messages in system log and
+ performance decreasing. Please, remember that superfluos output
+ option is depended implicitly from options that enable output of
+ concrete modules of NILFS2 driver.
+
endif # NILFS2_DEBUG_SUBSYSTEMS
endif # NILFS2_DEBUG
diff --git a/fs/nilfs2/debug.h b/fs/nilfs2/debug.h
index a85454c..3f3b42b 100644
--- a/fs/nilfs2/debug.h
+++ b/fs/nilfs2/debug.h
@@ -98,6 +98,17 @@
*/
#define DBG_DUMP_STACK 0x20000000
+/*
+ * This flag enables output from frequently called functions or
+ * detailed debugging output from function's body. Please, be
+ * cautious with enabling the option. Because it can be resulted
+ * in huge amount of debugging messages in system log and
+ * performance decreasing. Please, remember that superfluos output
+ * option is depended implicitly from options that enable output of
+ * concrete modules of NILFS2 driver.
+ */
+#define DBG_SPAM 0x40000000
+
#ifdef CONFIG_NILFS2_DEBUG
/* Definition of flags' set for debugging */
@@ -129,6 +140,9 @@ static u32 DBG_MASK = (
#ifdef CONFIG_NILFS2_DEBUG_DUMP_STACK
DBG_DUMP_STACK |
#endif /* CONFIG_NILFS2_DEBUG_DUMP_STACK */
+#ifdef CONFIG_NILFS2_DEBUG_SHOW_SPAM
+ DBG_SPAM |
+#endif /* CONFIG_NILFS2_DEBUG_SHOW_SPAM */
0);
#define NILFS2_SUBSYS_MASK 0x0FFFFFFF
@@ -143,10 +157,16 @@ static u32 DBG_MASK = (
#define nilfs2_debug(flg, f, a...) \
do { \
+ bool can_print_spam = DBG_MASK & DBG_SPAM; \
+ bool is_spam = flg & DBG_SPAM; \
bool can_dump_stack = DBG_MASK & DBG_DUMP_STACK; \
bool should_dump_stack = flg & DBG_DUMP_STACK; \
if ((flg & NILFS2_SUBSYS_MASK) & DBG_MASK) { \
- nilfs2_printk(f, ## a); \
+ if (is_spam) { \
+ if (can_print_spam) \
+ nilfs2_printk(f, ## a); \
+ } else \
+ nilfs2_printk(f, ## a); \
if (can_dump_stack && should_dump_stack) \
dump_stack(); \
} \
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2013-06-17 12:25 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=1371471949.2075.150.camel@slavad-ubuntu \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).