From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Paul Mackerras <paulus@samba.org>,
Vegard Nossum <vegardno@ifi.uio.no>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [BUG] perf and kmemcheck : fatal combination
Date: Tue, 26 Apr 2011 14:33:08 +0200 [thread overview]
Message-ID: <1303821188.20212.264.camel@twins> (raw)
In-Reply-To: <1303820855.3358.49.camel@edumazet-laptop>
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?
next prev parent reply other threads:[~2011-04-26 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 16:08 [BUG] perf and kmemcheck : fatal combination Eric Dumazet
2011-04-26 7:38 ` Peter Zijlstra
2011-04-26 7:43 ` Pekka Enberg
2011-04-26 8:04 ` Ingo Molnar
2011-04-26 8:57 ` Eric Dumazet
2011-04-26 9:53 ` Eric Dumazet
2011-04-26 10:08 ` Pekka Enberg
2011-04-26 10:27 ` Eric Dumazet
2011-04-26 12:27 ` Eric Dumazet
2011-04-26 12:33 ` Peter Zijlstra [this message]
2011-04-26 12:56 ` Eric Dumazet
2011-04-26 13:09 ` Eric Dumazet
2011-04-26 19:13 ` Pekka Enberg
2011-04-26 13:53 ` Mathieu Desnoyers
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=1303821188.20212.264.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
--cc=vegardno@ifi.uio.no \
/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.