[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1303821188.20212.264.camel@twins>
Date: Tue, 26 Apr 2011 14:33:08 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Pekka Enberg <penberg@...nel.org>, 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: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?
--
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