From: Catalin Marinas <catalin.marinas@arm.com>
To: Prateek Patel <prpatel@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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,
treding@nvidia.com
Subject: Re: [PATCH V2] kmemleak: Add config to select auto scan
Date: Wed, 12 Dec 2018 10:14:49 +0000 [thread overview]
Message-ID: <20181212101448.GA65138@arrakis.emea.arm.com> (raw)
In-Reply-To: <a51a7d4b-6366-ea10-f220-992525ec1d42@nvidia.com>
On Wed, Dec 12, 2018 at 12:14:29PM +0530, Prateek Patel wrote:
> On 10/29/2018 4:13 PM, Catalin Marinas wrote:
> > On Mon, Oct 22, 2018 at 11:38:43PM +0530, Prateek Patel wrote:
> > > From: Sri Krishna chowdary <schowdary@nvidia.com>
> > >
> > > Kmemleak scan can be cpu intensive and can stall user tasks at times.
> > > To prevent this, add config DEBUG_KMEMLEAK_AUTO_SCAN to enable/disable
> > > auto scan on boot up.
> > > Also protect first_run with DEBUG_KMEMLEAK_AUTO_SCAN as this is meant
> > > for only first automatic scan.
> > >
> > > Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
> > > Signed-off-by: Sachin Nikam <snikam@nvidia.com>
> > > Signed-off-by: Prateek <prpatel@nvidia.com>
> > Looks fine to me.
> >
> > Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>
> Can you mark this patch as acknowledged so that it can be picked up by the
> maintainer.
I thought Reviewed-by was sufficient. Anyway:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
prev parent reply other threads:[~2018-12-12 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 18:08 [PATCH V2] kmemleak: Add config to select auto scan Prateek Patel
2018-10-29 10:43 ` Catalin Marinas
2018-12-12 6:44 ` Prateek Patel
2018-12-12 10:14 ` 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=20181212101448.GA65138@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-tegra@vger.kernel.org \
--cc=prpatel@nvidia.com \
--cc=snikam@nvidia.com \
--cc=swarren@nvidia.com \
--cc=talho@nvidia.com \
--cc=treding@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).