From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: David Ahern <dsahern@gmail.com>,
Chulmin Kim <cmkim@core.kaist.ac.kr>,
linux-perf-users@vger.kernel.org
Subject: Re: perf top -z not working?
Date: Mon, 22 Oct 2012 12:04:18 -0400 [thread overview]
Message-ID: <50856E82.8000903@cs.utoronto.ca> (raw)
In-Reply-To: <20121022144552.GB8775@ghostprotocols.net>
On 22/10/2012 10:45 AM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 22, 2012 at 10:10:25AM -0400, Ryan Johnson escreveu:
>> On 22/10/2012 9:12 AM, David Ahern wrote:
>>> The kernel has nothing to do with the feature. From builtin-top.c,
>>> this part is either not happening or more likely not happening
>>> correctly.
>>>
>>> if (top->zero)
>>> symbol__annotate_zero_histogram(symbol, top->sym_evsel->idx);
>>> else
>>> symbol__annotate_decay_histogram(symbol, top->sym_evsel->idx);
>>>
>>> I recall it working recently - last year or so. Can you try
>>> different versions -- say 3.0, 3.2, 3.4 and latest? If you have a
>>> copy of Linus' tree or Arnaldo's git tree it should not take much
>>> time.
>> Chulmin says his 3.0 version works. My 3.2.18 doesn't. I don't have
>> a copy of the git tree on that machine, but I'll try building 3.4.x
>> and tip when I get a chance. I have never built perf-tools before,
>> though, so I'd appreciate tips on what might be different for
>> building perf-tools compared to the kernel, and how to avoid
>> building the standard kernel along the way. Hopefully it's just
>> configure-make-install?
> To build just the tools, on a /usr/src/linux or wherever you have the
> newer kernel sources:
>
> make -C tools/perf install
>
> Then make sure you use what is in your ~/bin/ before the standard path:
>
> export PATH=~/bin:$PATH
> hash -r
>
> Then try perf top -z again.
OK! That doesn't sound bad at all.
Thanks,
Ryan
next prev parent reply other threads:[~2012-10-22 16:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 12:26 perf top -z not working? Ryan Johnson
2012-10-17 13:49 ` Chulmin Kim
2012-10-22 1:46 ` Arnaldo Carvalho de Melo
2012-10-22 11:50 ` Ryan Johnson
2012-10-22 13:12 ` David Ahern
2012-10-22 14:10 ` Ryan Johnson
2012-10-22 14:13 ` Chulmin Kim
2012-10-22 14:15 ` Chulmin Kim
2012-10-22 14:45 ` Arnaldo Carvalho de Melo
2012-10-22 15:01 ` David Ahern
2012-10-22 16:04 ` Ryan Johnson [this message]
2012-10-23 6:04 ` Namhyung Kim
2012-10-23 16:10 ` David Ahern
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=50856E82.8000903@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=acme@ghostprotocols.net \
--cc=cmkim@core.kaist.ac.kr \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).