From: Randy Dunlap <randy.dunlap@oracle.com>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] initcall: add config option for compiling initcall_debug
Date: Sun, 27 Mar 2011 10:43:32 -0700 [thread overview]
Message-ID: <20110327104332.6703de4c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110327115506.14008.17733.stgit@localhost6>
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@openvz.org>
> ---
> 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 ***
next prev parent reply other threads:[~2011-03-27 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 11:55 Konstantin Khlebnikov
2011-03-27 17:43 ` Randy Dunlap [this message]
2011-03-28 7:53 ` Konstantin Khlebnikov
2011-03-28 7:51 ` [PATCH v2 typo-fixed] " Konstantin Khlebnikov
2011-03-29 22:57 ` Andrew Morton
2011-03-30 22:31 ` Rafael J. Wysocki
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=20110327104332.6703de4c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--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
Powered by JetHome