From: David Ahern <dsahern@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>,
Ryan Johnson <ryan.johnson@cs.utoronto.ca>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Chulmin Kim <cmkim@core.kaist.ac.kr>, linux-perf-users@vger.kernel.org
Subject: Re: perf top -z not working?
Date: Tue, 23 Oct 2012 10:10:07 -0600 [thread overview]
Message-ID: <5086C15F.9020109@gmail.com> (raw)
In-Reply-To: <8762617mi6.fsf@sejong.aot.lge.com>
took a minute to bisect it this morning:
$ git bisect good
ab81f3fd350c510730adb1ca40ef55c2b2952121 is the first bad commit
commit ab81f3fd350c510730adb1ca40ef55c2b2952121
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Wed Oct 5 19:16:15 2011 -0300
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
prev parent reply other threads:[~2012-10-23 16:10 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
2012-10-23 6:04 ` Namhyung Kim
2012-10-23 16:10 ` David Ahern [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=5086C15F.9020109@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=cmkim@core.kaist.ac.kr \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ryan.johnson@cs.utoronto.ca \
/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.