From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
catalin.marinas@arm.com, corbet@lwn.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: Add CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF case
Date: Fri, 24 Oct 2014 12:10:25 -0700 [thread overview]
Message-ID: <544AA421.6040705@infradead.org> (raw)
In-Reply-To: <1414153500-29150-3-git-send-email-standby24x7@gmail.com>
On 10/24/14 05:25, Masanari Iida wrote:
> This patch add a case with CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> Documentation/kmemleak.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
> index f4f033c..0f2bbd8 100644
> --- a/Documentation/kmemleak.txt
> +++ b/Documentation/kmemleak.txt
> @@ -62,6 +62,10 @@ Memory may be allocated or freed before kmemleak is initialised and
> these actions are stored in an early log buffer. The size of this buffer
> is configured via the CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE option.
>
> +If CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF are enabled, the kmemleak is
is enabled, kmemleak is
> +disabled by default. Passing "kmemleak=on" on the kernel command
> +line enables the function.
> +
> Basic Algorithm
> ---------------
>
>
--
~Randy
next prev parent reply other threads:[~2014-10-24 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 12:24 [PATCH 0/2] Documenation: kmemleak: Add an explanation about CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y case Masanari Iida
2014-10-24 12:24 ` [PATCH 1/2] Documentation: Add default kmemleak off case in kernel-parameters.txt Masanari Iida
2014-10-24 12:25 ` [PATCH 2/2] Documentation: Add CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF case Masanari Iida
2014-10-24 19:10 ` Randy Dunlap [this message]
2014-10-24 15:52 ` [PATCH 0/2] Documenation: kmemleak: Add an explanation about CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y case Catalin Marinas
2014-10-24 17:59 ` Jonathan Corbet
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=544AA421.6040705@infradead.org \
--to=rdunlap@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
/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