From: Peter Zijlstra <peterz@infradead.org>
To: Sylvain GENEVES <Sylvain.Geneves@inrialpes.fr>
Cc: "oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robert.richter" <robert.richter@amd.com>
Subject: Re: Oprofile bug ?
Date: Sat, 13 Nov 2010 17:18:36 +0100 [thread overview]
Message-ID: <1289665116.2084.887.camel@laptop> (raw)
In-Reply-To: <c69374315a434a8bab96c55e4542bc81.squirrel@webmail.inrialpes.fr>
On Fri, 2010-11-12 at 22:11 +0100, Sylvain GENEVES wrote:
> Anyone has any idea on what is happening ?
Yeah, the oprofile code is terminally broken, it uses
__copy_from_user_inatomic() from NMI context.
prev parent reply other threads:[~2010-11-13 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 21:11 Oprofile bug ? Sylvain GENEVES
2010-11-12 21:45 ` Frank Ch. Eigler
2010-11-13 16:18 ` Peter Zijlstra [this message]
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=1289665116.2084.887.camel@laptop \
--to=peterz@infradead.org \
--cc=Sylvain.Geneves@inrialpes.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=robert.richter@amd.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