From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Zeno Davatz <zdavatz@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kmemleak, cpu usage jump out of nowhere
Date: Wed, 14 Jul 2010 12:55:56 +0300 [thread overview]
Message-ID: <4C3D89AC.4040303@cs.helsinki.fi> (raw)
In-Reply-To: <1279100846.8592.53.camel@e102109-lin.cambridge.arm.com>
Catalin Marinas wrote:
> On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
>> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>
>>>> I am attaching you the file from /sys/kernel/debug/kmemleak
>>> Zeno, can you post your dmesg and .config, please?
>> Sure, see attached files.
>
> It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
> need to post it again on the list).
>
>
> kmemleak: Add support for NO_BOOTMEM configurations
>
> From: Catalin Marinas <catalin.marinas@arm.com>
>
> With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
> friends use the early_res functions for memory management when
> NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
> corresponding code paths for bootmem allocations.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Cc: H. Peter Anvin <hpa@zytor.com>
Makes sense.
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Zeno, this should fix the kmemleak false positives but not the big
pauses you're seeing.
next prev parent reply other threads:[~2010-07-14 9:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 6:12 kmemleak, cpu usage jump out of nowhere Zeno Davatz
2010-07-14 8:05 ` Pekka Enberg
2010-07-14 8:27 ` Zeno Davatz
2010-07-14 9:47 ` Catalin Marinas
2010-07-14 9:55 ` Pekka Enberg [this message]
2010-07-14 10:00 ` Zeno Davatz
2010-07-15 14:58 ` Catalin Marinas
2010-07-15 15:15 ` Zeno Davatz
2010-07-15 15:54 ` Pekka Enberg
2010-07-15 16:28 ` Damien Wyart
2010-07-15 19:16 ` Damien Wyart
2010-07-15 19:50 ` Pekka Enberg
2010-07-15 20:00 ` Damien Wyart
2010-07-15 20:38 ` Zeno Davatz
2010-07-15 20:50 ` Pekka Enberg
2010-07-15 20:57 ` Zeno Davatz
2010-07-16 7:12 ` Zeno Davatz
2010-07-16 7:29 ` Zeno Davatz
2010-07-16 7:37 ` Zeno Davatz
2010-07-16 7:50 ` Pekka Enberg
2010-07-16 9:17 ` Zeno Davatz
2010-07-16 9:32 ` Pekka Enberg
2010-07-16 9:42 ` Zeno Davatz
2010-07-16 9:47 ` Zeno Davatz
2010-07-16 18:27 ` Yinghai Lu
2010-07-16 20:29 ` Zeno Davatz
2010-07-16 20:59 ` Yinghai Lu
2010-07-17 8:46 ` Zeno Davatz
2010-07-15 20:52 ` Pekka Enberg
2010-08-03 9:05 ` Peter Zijlstra
2010-08-03 9:11 ` Zeno Davatz
2010-08-03 9:15 ` damien.wyart
2010-08-03 9:18 ` Zeno Davatz
2010-08-20 9:32 ` Damien Wyart
2010-08-20 9:40 ` Peter Zijlstra
2010-07-14 8:31 ` Damien Wyart
2010-07-14 8:34 ` Zeno Davatz
2010-07-14 8:38 ` Pekka Enberg
2010-07-14 8:54 ` Zeno Davatz
2010-07-14 8:57 ` Pekka Enberg
2010-07-14 9:57 ` Catalin Marinas
2010-07-14 10:04 ` Zeno Davatz
2010-07-14 11:54 ` Catalin Marinas
2010-07-14 11:59 ` Zeno Davatz
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=4C3D89AC.4040303@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zdavatz@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