From: Andi Kleen <andi@firstfloor.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
acme@kernel.org, peterz@infradead.org, jolsa@kernel.org,
mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Add top down metrics to perf stat
Date: Thu, 19 May 2016 16:51:30 -0700 [thread overview]
Message-ID: <20160519235130.GO13997@two.firstfloor.org> (raw)
In-Reply-To: <20160516125838.GD10877@krava>
On Mon, May 16, 2016 at 02:58:38PM +0200, Jiri Olsa wrote:
> On Fri, May 13, 2016 at 06:44:49PM -0700, Andi Kleen wrote:
>
> SNIP
>
> >
> > The formulas to compute the metrics are generic, they
> > only change based on the availability on the abstracted
> > input values.
> >
> > The kernel declares the events supported by the current
> > CPU and perf stat then computes the formulas based on the
> > available metrics.
> >
> >
> > Example output:
> >
> > $ perf stat --topdown -I 1000 cmd
> > 1.000735655 frontend bound retiring bad speculation backend bound
> > 1.000735655 S0-C0 2 47.84% 11.69% 8.37% 32.10%
> > 1.000735655 S0-C1 2 45.53% 11.39% 8.52% 34.56%
Hi Jiri,
>
> you've lost first 3 header lines (time/core/cpus):
>
> [jolsa@ibm-x3650m4-01 perf]$ sudo ./perf stat --per-core -e cycles -I 1000 -a
> # time core cpus counts unit events
> 1.000310344 S0-C0 2 3,764,470,414 cycles
> 1.000310344 S0-C1 2 3,764,445,293 cycles
> 1.000310344 S0-C2 2 3,764,428,422 cycles
I can't reproduce that.
The headers look the same as before.
>
> also I'm still getting -0% as I mentioned in my previous comment:
Keeping the NMI watchdog enabled can make the formulas inaccurate
because the grouping is disabled, and parts of the formulas
may be measured at different times where the execution profile
is different.
But anyways even without that it can be caused by small inaccuracies,
and then during rounding the value rounds to 0.
I can remove the - for this case.
Otherwise the data looks reasonable.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2016-05-19 23:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 1:44 Add top down metrics to perf stat Andi Kleen
2016-05-14 1:44 ` [PATCH 1/8] x86/topology: Add topology_max_smt_threads() Andi Kleen
2016-05-14 1:44 ` [PATCH 2/8] perf/x86: Support sysfs files depending on SMT status Andi Kleen
2016-05-14 1:44 ` [PATCH 3/8] perf/x86/intel: Add Top Down events to Intel Core Andi Kleen
2016-05-14 1:44 ` [PATCH 4/8] perf/x86/intel: Add Top Down events to Intel Atom Andi Kleen
2016-05-14 1:44 ` [PATCH 5/8] perf/x86/intel: Use new topology_max_smt_threads() in HT leak workaround Andi Kleen
2016-05-14 1:44 ` [PATCH 6/8] perf stat: Avoid fractional digits for integer scales Andi Kleen
2016-05-16 12:53 ` Jiri Olsa
2016-05-14 1:44 ` [PATCH 7/8] perf stat: Basic support for TopDown in perf stat Andi Kleen
2016-05-14 1:44 ` [PATCH 8/8] perf stat: Add computation of TopDown formulas Andi Kleen
2016-05-20 10:23 ` Jiri Olsa
2016-05-20 13:38 ` Andi Kleen
2016-05-20 13:43 ` Jiri Olsa
2016-05-20 14:15 ` Andi Kleen
2016-05-20 13:43 ` Andi Kleen
2016-05-16 12:58 ` Add top down metrics to perf stat Jiri Olsa
2016-05-19 23:51 ` Andi Kleen [this message]
2016-05-20 9:59 ` Jiri Olsa
2016-05-20 14:18 ` Andi Kleen
2016-05-20 10:24 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2016-05-20 0:09 Andi Kleen
2016-05-05 23:03 Andi Kleen
2016-05-12 7:47 ` Jiri Olsa
2016-04-27 20:00 Andi Kleen
2016-04-04 20:41 Andi Kleen
2016-03-22 23:08 Andi Kleen
2016-03-27 11:27 ` Jiri Olsa
2016-03-27 15:22 ` Andi Kleen
2016-01-20 2:27 Andi Kleen
2016-01-16 1:12 Andi Kleen
2015-08-08 1:06 Andi Kleen
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=20160519235130.GO13997@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 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.