Re: [PATCH] initcall: add config option for compilinginitcall_debug

From: Randy Dunlap
Date: Sun Mar 27 2011 - 13:44:24 EST


On Sun, 27 Mar 2011 15:55:06 +0400 Konstantin Khlebnikov wrote:

> Add bool config option CONFIG_INITCALL_DEBUG for compiling initcalls debuging,
> make it on by default to keep current behaviour.

Typo fixes only:


> Signed-off-by: Konstantin Khlebnikov <khlebnikov@xxxxxxxxxx>
> ---
> Documentation/kernel-parameters.txt | 2 +-
> include/linux/init.h | 4 ++++
> init/main.c | 2 ++
> kernel/async.c | 4 +---
> lib/Kconfig.debug | 7 +++++++
> 5 files changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index c357a31..ea3843a 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -970,7 +970,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>
> initcall_debug [KNL] Trace initcalls as they are executed. Useful
> for working out where the kernel is dying during
> - startup.
> + startup. This depend on CONFIG_INITCALL_DEBUG option.

depends on the CONFIG_INITCALL_DEBUG option.

>
> initrd= [BOOT] Specify the location of the initial ramdisk


> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index df9234c..ebc1357 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -807,6 +807,13 @@ config DEBUG_CREDENTIALS
>
> If unsure, say N.
>
> +config INITCALL_DEBUG
> + bool "Debug kernel initcalls"
> + default y
> + help
> + This build option allow you trace initcalls after

allows you to trace initcalls by

> + adding "initcall_debug" to kernel command line.

to the kernel command line.

> +
> #
> # Select this config option from the architecture Kconfig, if it
> # it is preferred to always offer frame pointers as a config


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/