From: Catalin Marinas <catalin.marinas@arm.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: subscriptions@stroomer.com, linux-mm@kvack.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kmemleak for mips
Date: Tue, 03 Nov 2009 09:23:47 +0000 [thread overview]
Message-ID: <1257240227.22183.3.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <43e72e890911020907m7cfc48edpd300243de7af36ed@mail.gmail.com>
On Mon, 2009-11-02 at 09:07 -0800, Luis R. Rodriguez wrote:
> Curious what the limitations are on restricting kmemleak to non-mips
> archs. I have a user and situation [1] where this could be helpful [1]
> in debugging an issue. The user reports he cannot enable it on mips.
It may just work but cannot be enabled because I cannot test kmemleak on
such hardware. In general you need to make sure that the _sdata/_edata
and __bss_start/__bss_stop symbols are defined. If there are other ways
of allocating memory than the standard API, it would need additional
hooks. Some false-positives specific to MIPS may need to be annotated
(usually with kmemleak_not_leak).
(btw, you could also merge the kmemleak.git tree on git.kernel.org as it
has improvements on the rate of false positives; the patches will be
pushed in 2.6.33-rc1)
--
Catalin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-03 9:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 17:07 Luis R. Rodriguez
2009-11-03 9:23 ` Catalin Marinas [this message]
2010-03-02 13:54 kmemleak for MIPS naveen yadav
2011-03-24 9:27 ` Daniel Baluta
2011-03-24 9:55 ` Catalin Marinas
2011-03-28 21:15 ` Maxin John
2011-03-29 10:40 ` Catalin Marinas
2011-03-29 11:38 ` Maxin John
2011-03-29 11:50 ` Catalin Marinas
2011-03-29 12:27 ` Maxin John
2011-03-29 19:36 ` Maxin John
2011-03-29 19:54 ` Daniel Baluta
2011-03-30 9:15 ` Catalin Marinas
2011-03-30 9:54 ` Daniel Baluta
2011-03-30 9:58 ` Catalin Marinas
2011-03-30 11:03 ` Maxin John
2011-03-30 11:24 ` Daniel Baluta
2011-03-30 11:38 ` Catalin Marinas
2011-03-30 12:17 ` Maxin John
2011-03-30 12:27 ` Eric Dumazet
2011-03-30 12:40 ` Maxin John
2011-03-30 12:52 ` Daniel Baluta
2011-03-30 13:17 ` Maxin John
2011-03-30 13:27 ` Eric Dumazet
2011-03-30 14:07 ` Maxin John
2011-03-30 14:07 ` Catalin Marinas
2011-03-30 12:22 ` Eric Dumazet
2011-03-30 10:08 ` Maxin John
2011-03-30 14:28 ` Ralf Baechle
2011-03-30 14:21 ` Ralf Baechle
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=1257240227.22183.3.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=penberg@cs.helsinki.fi \
--cc=subscriptions@stroomer.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