From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] DEBUG_KERNEL menu cleanups
Date: Fri, 14 Apr 2006 13:18:53 +0200 [thread overview]
Message-ID: <20060414111853.GG4162@stusta.de> (raw)
This patch contains the following possible cleanups:
- move DEBUG_FS above the DEBUG_KERNEL options (it did break the menu)
- let the following options depend on DEBUG_KERNEL:
- PRINTK_TIME
- DEBUG_SHIRQ
- RT_MUTEX_TESTER
- UNWIND_INFO
- fix the formatting of the DEBUG_SHIRQ help text
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
lib/Kconfig.debug | 59 +++++++++++++++++++++++-----------------------
1 file changed, 30 insertions(+), 29 deletions(-)
--- linux-2.6.17-rc1-mm2-full/lib/Kconfig.debug.old 2006-04-14 13:05:39.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/lib/Kconfig.debug 2006-04-14 13:13:10.000000000 +0200
@@ -1,14 +1,4 @@
-config PRINTK_TIME
- bool "Show timing information on printks"
- help
- Selecting this option causes timing information to be
- included in printk output. This allows you to measure
- the interval between kernel operations, including bootup
- operations. This is useful for identifying long delays
- in kernel startup.
-
-
config MAGIC_SYSRQ
bool "Magic SysRq key"
depends on !UML
@@ -23,14 +13,15 @@
keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
unless you really know what this hack does.
-config DEBUG_SHIRQ
- bool "Debug shared IRQ handlers"
- depends on GENERIC_HARDIRQS
- help
- Enable this to generate a spurious interrupt as soon as a shared interrupt
- handler is registered, and just before one is deregistered. Drivers ought
- to be able to handle interrupts coming in at those points; some don't and
- need to be caught.
+config DEBUG_FS
+ bool "Debug Filesystem"
+ depends on SYSFS
+ help
+ debugfs is a virtual file system that kernel developers use to put
+ debugging files into. Enable this option to be able to read and
+ write to these files.
+
+ If unsure, say N.
config DEBUG_KERNEL
bool "Kernel debugging"
@@ -38,6 +29,25 @@
Say Y here if you are developing drivers or trying to debug and
identify kernel problems.
+config PRINTK_TIME
+ bool "Show timing information on printks"
+ depends on DEBUG_KERNEL
+ help
+ Selecting this option causes timing information to be
+ included in printk output. This allows you to measure
+ the interval between kernel operations, including bootup
+ operations. This is useful for identifying long delays
+ in kernel startup.
+
+config DEBUG_SHIRQ
+ bool "Debug shared IRQ handlers"
+ depends on GENERIC_HARDIRQS && DEBUG_KERNEL
+ help
+ Enable this to generate a spurious interrupt as soon as a shared
+ interrupt handler is registered, and just before one is deregistered.
+ Drivers ought to be able to handle interrupts coming in at those
+ points; some don't and need to be caught.
+
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
range 12 21
@@ -136,7 +146,7 @@
config RT_MUTEX_TESTER
bool "Built-in scriptable tester for rt-mutexes"
- depends on RT_MUTEXES
+ depends on RT_MUTEXES && DEBUG_KERNEL
default n
help
This option enables a rt-mutex tester.
@@ -201,16 +211,6 @@
If unsure, say N.
-config DEBUG_FS
- bool "Debug Filesystem"
- depends on SYSFS
- help
- debugfs is a virtual file system that kernel developers use to put
- debugging files into. Enable this option to be able to read and
- write to these files.
-
- If unsure, say N.
-
config DEBUG_VM
bool "Debug VM"
depends on DEBUG_KERNEL
@@ -232,6 +232,7 @@
config UNWIND_INFO
bool "Compile the kernel with frame unwind information"
+ depends on DEBUG_KERNEL
depends on !IA64
depends on !MODULES || !(MIPS || PARISC || PPC || SUPERH || SPARC64 || V850)
help
next reply other threads:[~2006-04-14 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 11:18 Adrian Bunk [this message]
2006-04-14 12:36 ` [RFC: 2.6 patch] DEBUG_KERNEL menu cleanups Sam Ravnborg
2006-04-19 16:43 ` Adrian Bunk
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=20060414111853.GG4162@stusta.de \
--to=bunk@stusta.de \
--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.