From: Catalin Marinas <catalin.marinas@arm.com>
To: Li Zefan <lizefan@huawei.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Run-time kernel checking
Date: Thu, 15 May 2014 14:23:03 +0100 [thread overview]
Message-ID: <20140515132302.GB1499@arm.com> (raw)
In-Reply-To: <53709571.9020204@huawei.com>
On Mon, May 12, 2014 at 10:33:37AM +0100, Li Zefan wrote:
> Another one is supporting re-enablement of kmemleak, which you already saw the
> patch and expressed your NACK.
>
> https://lkml.org/lkml/2014/1/17/102
And I nack'ed it for good reasons ;). But since you haven't explained
your reasons, I haven't followed up with any alternative solutions (for
example, if overhead is what you are after, you could have specific
kmemleak options to still track objects but for example don't save a
stack trace for each allocation).
--
Catalin
prev parent reply other threads:[~2014-05-15 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 10:04 [Ksummit-discuss] [CORE TOPIC] Run-time kernel checking Catalin Marinas
2014-05-12 9:33 ` Li Zefan
2014-05-15 13:23 ` 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=20140515132302.GB1499@arm.com \
--to=catalin.marinas@arm.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=lizefan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.