From: Catalin Marinas <catalin.marinas@arm.com>
To: Prateek Patel <prpatel@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-tegra@vger.kernel.org, snikam@nvidia.com,
vdumpa@nvidia.com, talho@nvidia.com, swarren@nvidia.com,
Sri Krishna chowdary <schowdary@nvidia.com>
Subject: Re: [PATCH] kmemleak: Add config to select auto scan
Date: Wed, 17 Oct 2018 14:41:09 +0100 [thread overview]
Message-ID: <20181017134109.GA223677@arrakis.emea.arm.com> (raw)
In-Reply-To: <1539763408-22085-1-git-send-email-prpatel@nvidia.com>
On Wed, Oct 17, 2018 at 01:33:28PM +0530, Prateek Patel wrote:
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index e5e7c03..9542852 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -593,6 +593,17 @@ config DEBUG_KMEMLEAK_DEFAULT_OFF
> Say Y here to disable kmemleak by default. It can then be enabled
> on the command line via kmemleak=on.
>
> +config DEBUG_KMEMLEAK_SCAN_ON
Nitpick: DEBUG_KMEMLEAK_AUTO_SCAN may be a better name since you don't
aim to disable scanning altogether.
> + bool "Enable kmemleak auto scan thread on boot up"
> + default y
> + depends on DEBUG_KMEMLEAK
> + help
> + Kmemleak scan is cpu intensive and can stall user tasks at times.
I guess that depends on the CPU.
> + This option enables/disables automatic kmemleak scan at boot up.
> +
> + Say N here to disable kmemleak auto scan thread to stop automatic
> + scanning.
You should also mention that disabling this option also disables
automatic reporting of memory leaks. And I'd add a "if unsure, say Y".
> +
> config DEBUG_STACK_USAGE
> bool "Stack utilization instrumentation"
> depends on DEBUG_KERNEL && !IA64
> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> index 877de4f..ac53678 100644
> --- a/mm/kmemleak.c
> +++ b/mm/kmemleak.c
> @@ -1647,11 +1647,14 @@ static void kmemleak_scan(void)
> */
> static int kmemleak_scan_thread(void *arg)
> {
> +#ifdef CONFIG_DEBUG_KMEMLEAK_SCAN_ON
> static int first_run = 1;
> +#endif
static int first_run = IS_ENABLED(CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN);
>
> pr_info("Automatic memory scanning thread started\n");
> set_user_nice(current, 10);
>
> +#ifdef CONFIG_DEBUG_KMEMLEAK_SCAN_ON
> /*
> * Wait before the first scan to allow the system to fully initialize.
> */
> @@ -1661,6 +1664,7 @@ static int kmemleak_scan_thread(void *arg)
> while (timeout && !kthread_should_stop())
> timeout = schedule_timeout_interruptible(timeout);
> }
> +#endif
With the first_run change above, this #ifdef is no longer needed.
>
> while (!kthread_should_stop()) {
> signed long timeout = jiffies_scan_wait;
> @@ -2141,9 +2145,11 @@ static int __init kmemleak_late_init(void)
> return -ENOMEM;
> }
>
> +#ifdef CONFIG_DEBUG_KMEMLEAK_SCAN_ON
> mutex_lock(&scan_mutex);
> start_scan_thread();
> mutex_unlock(&scan_mutex);
> +#endif
Please use:
if (IS_ENABLED(CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN)) {
...
}
--
Catalin
prev parent reply other threads:[~2018-10-17 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 8:03 [PATCH] kmemleak: Add config to select auto scan Prateek Patel
2018-10-17 13:41 ` Catalin Marinas [this message]
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=20181017134109.GA223677@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-tegra@vger.kernel.org \
--cc=prpatel@nvidia.com \
--cc=schowdary@nvidia.com \
--cc=snikam@nvidia.com \
--cc=swarren@nvidia.com \
--cc=talho@nvidia.com \
--cc=vdumpa@nvidia.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;
as well as URLs for NNTP newsgroup(s).