From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, peterz@infradead.org, jolsa@kernel.org,
eranian@google.com, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Add top down metrics to perf stat
Date: Sun, 27 Mar 2016 13:27:59 +0200 [thread overview]
Message-ID: <20160327112759.GE4015@krava.sund.root.ku.dk> (raw)
In-Reply-To: <1458688137-5946-1-git-send-email-andi@firstfloor.org>
On Tue, Mar 22, 2016 at 04:08:46PM -0700, Andi Kleen wrote:
SNIP
> In this case perf stat automatically enables --per-core mode and also requires
> global mode (-a) and avoiding other filters (no cgroup mode)
>
> When Hyper Threading is off this can be overriden with the --single-thread
> option. When Hyper Threading is on it is enforced, the only way to
> not require -a here is to off line the logical CPUs of the second
> threads.
>
> One side effect is that this may require root rights or a
> kernel.perf_event_paranoid=-1 setting.
>
> Full tree available in
> git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc perf/top-down-16
>
can't see this one (-16):
[jolsa@krava perf]$ git remote update ak
Fetching ak
[jolsa@krava perf]$ git branch -r | grep top-down
ak/perf/top-down-10
ak/perf/top-down-11
ak/perf/top-down-13
ak/perf/top-down-2
thanks,
jirka
next prev parent reply other threads:[~2016-03-27 11:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 23:08 Add top down metrics to perf stat Andi Kleen
2016-03-22 23:08 ` [PATCH 01/11] x86, perf: Support sysfs files depending on SMT status Andi Kleen
2016-03-22 23:08 ` [PATCH 02/11] x86, perf: Add Top Down events to Intel Core Andi Kleen
2016-03-22 23:08 ` [PATCH 03/11] x86, perf: Add Top Down events to Intel Atom Andi Kleen
2016-03-22 23:08 ` [PATCH 04/11] x86, perf: Use new ht_on flag in HT leak workaround Andi Kleen
2016-03-22 23:08 ` [PATCH 05/11] perf, tools: Parse an .aggr-per-core event attribute Andi Kleen
2016-03-22 23:08 ` [PATCH 06/11] perf, tools, stat: Force --per-core mode for .aggr-per-core aliases Andi Kleen
2016-03-22 23:08 ` [PATCH 07/11] perf, tools, stat: Avoid fractional digits for integer scales Andi Kleen
2016-03-22 23:08 ` [PATCH 08/11] perf, tools, stat: Scale values by unit before metrics Andi Kleen
2016-03-22 23:08 ` [PATCH 09/11] perf, tools, stat: Basic support for TopDown in perf stat Andi Kleen
2016-03-22 23:08 ` [PATCH 10/11] perf, tools, stat: Add computation of TopDown formulas Andi Kleen
2016-03-22 23:08 ` [PATCH 11/11] perf, tools, stat: Add extra output of counter values with -v Andi Kleen
2016-03-27 11:27 ` Jiri Olsa [this message]
2016-03-27 15:22 ` Add top down metrics to perf stat Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2016-05-20 0:09 Andi Kleen
2016-05-14 1:44 Andi Kleen
2016-05-16 12:58 ` Jiri Olsa
2016-05-19 23:51 ` Andi Kleen
2016-05-20 9:59 ` Jiri Olsa
2016-05-20 14:18 ` Andi Kleen
2016-05-20 10:24 ` Jiri Olsa
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-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=20160327112759.GE4015@krava.sund.root.ku.dk \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--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 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).