From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
anton@samba.org, mingo@elte.hu, ak@linux.intel.com,
Robert Richter <robert.richter@amd.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/4] perf symbols: /proc/kallsyms does not sort module symbols
Date: Fri, 23 Sep 2011 16:12:29 +0200 [thread overview]
Message-ID: <1316787149.9084.43.camel@twins> (raw)
In-Reply-To: <20110923141113.GA27519@ghostprotocols.net>
On Fri, 2011-09-23 at 11:11 -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 23, 2011 at 03:59:33PM +0200, Stephane Eranian escreveu:
> > Hi,
> >
> > What's the status of this patch?
> >
> > It is not in 3.1.0-rc7. It is needed!
> >
> > I ran into serious issues (bogus symbols) with a profile where
> > kernel modules were stressed and it boiled down to kallsyms__parse()
> > being broken because /proc/kallsyms is assumed sorted when it actually
> > is NOT.
>
> Its all here:
>
> https://github.com/acmel/linux/commits/perf/urgent
>
> I was waiting for Ingo, Peter, can you take a look and see if you agree
> with the patches there then I can ask Linus to pull it, ok?
Looks all-right, ship it! :-)
next prev parent reply other threads:[~2011-09-23 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 13:59 [PATCH 2/4] perf symbols: /proc/kallsyms does not sort module symbols Stephane Eranian
2011-09-23 14:11 ` Arnaldo Carvalho de Melo
2011-09-23 14:12 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-24 6:40 [PATCH 0/4] perf symbol fixes Anton Blanchard
2011-08-24 6:40 ` [PATCH 2/4] perf symbols: /proc/kallsyms does not sort module symbols Anton Blanchard
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=1316787149.9084.43.camel@twins \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=anton@samba.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=torvalds@linux-foundation.org \
/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