[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1303845192.15231.113.camel@jaguar>
Date: Tue, 26 Apr 2011 22:13:12 +0300
From: Pekka Enberg <penberg@...nel.org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Eric Dumazet <eric.dumazet@...il.com>, Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Paul Mackerras <paulus@...ba.org>,
Vegard Nossum <vegardno@....uio.no>,
linux-kernel <linux-kernel@...r.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [BUG] perf and kmemcheck : fatal combination
On Tue, 2011-04-26 at 14:33 +0200, Peter Zijlstra wrote:
> On Tue, 2011-04-26 at 14:27 +0200, Eric Dumazet wrote:
> > Thats far from trivial, maybe because we dont have NOTRACK api for
> > percpu allocations ?
>
> We can't use per-cpu allocations from NMI context because of the same
> problem, per-cpu uses vmalloc and vmalloc needs faults. Hence that
> shouldn't be a problem.
>
> It looks like you covered most of it though, the buffer and the
> callchain stuff, aside from that it should only use some static data.
>
> Pekka, what does kmemcheck do for .data and .bss things?
No, kmemcheck is only active for memory allocated with slab and the page
allocator .
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists