From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Add fine grained sampled metrics for perf script
Date: Thu, 23 Nov 2017 14:46:17 -0300 [thread overview]
Message-ID: <20171123174617.GK8789@kernel.org> (raw)
In-Reply-To: <20171123074742.GA5587@krava>
Em Thu, Nov 23, 2017 at 08:47:42AM +0100, Jiri Olsa escreveu:
> On Fri, Nov 17, 2017 at 01:42:57PM -0800, Andi Kleen wrote:
>
> SNIP
>
> > TopDown:
> >
> > Note TopDown requires disabling SMT if you have it enabled (e.g. by offlining
> > the extra CPUs), because SMT would require sampling per core, which is not supported.
> >
> > $ perf record -e '{ref-cycles,topdown-fetch-bubbles,topdown-recovery-bubbles,\
> > topdown-slots-retired,topdown-total-slots,topdown-slots-issued}:S' -a sleep 1
> > $ perf script --header -I -F cpu,ip,sym,event,metric,period
> > ...
> > [000] 121108 ref-cycles: ffffffff8165222e copy_user_enhanced_fast_string
> > [000] 190350 topdown-fetch-bubbles: ffffffff8165222e copy_user_enhanced_fast_string
> > [000] 2055 topdown-recovery-bubbles: ffffffff8165222e copy_user_enhanced_fast_string
> > [000] 148729 topdown-slots-retired: ffffffff8165222e copy_user_enhanced_fast_string
> > [000] 144324 topdown-total-slots: ffffffff8165222e copy_user_enhanced_fast_string
> > [000] 160852 topdown-slots-issued: ffffffff8165222e copy_user_enhanced_fast_string
> > [000] metric: 33.0% frontend bound
> > [000] metric: 3.5% bad speculation
> > [000] metric: 25.8% retiring
> > [000] metric: 37.7% backend bound
> > [000] 112112 ref-cycles: ffffffff8165aec8 _raw_spin_lock_irqsave
> > [000] 357222 topdown-fetch-bubbles: ffffffff8165aec8 _raw_spin_lock_irqsave
> > [000] 3325 topdown-recovery-bubbles: ffffffff8165aec8 _raw_spin_lock_irqsave
> > [000] 323553 topdown-slots-retired: ffffffff8165aec8 _raw_spin_lock_irqsave
> > [000] 270507 topdown-total-slots: ffffffff8165aec8 _raw_spin_lock_irqsave
> > [000] 341226 topdown-slots-issued: ffffffff8165aec8 _raw_spin_lock_irqsave
> > [000] metric: 33.0% frontend bound
> > [000] metric: 2.9% bad speculation
> > [000] metric: 29.9% retiring
> > [000] metric: 34.2% backend bound
> >
> >
> > Git tree:
> > git://git.kernel.org/pub/scm/limux/kernel/git/ak/linux-misc.git perf/script-metric-3
> >
> >
> > v1: Initial post
> > v2:
> > Remove already merged patches.
> > Use evsel->priv for new fields
> > Port to new base line, support fp output.
> > Handle stats in ->stats, not ->priv
> > Minor cleanups
> > v3:
> > Enable EVENT_UPDATE in perf record, and record unit/scale/cpu map/thread map
> > Drop the previous zero cpu map hack.
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks, applied, and added the detailed explanation about the use of the
term 'averaging' done by Andi,
- Arnaldo
next prev parent reply other threads:[~2017-11-23 17:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 21:42 Add fine grained sampled metrics for perf script Andi Kleen
2017-11-17 21:42 ` [PATCH v3 1/3] perf, tools, record: Synthesize unit/scale/... in event update Andi Kleen
2017-12-06 16:31 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2017-11-17 21:42 ` [PATCH v3 2/3] perf, tools, record: Synthesize thread map and cpu map Andi Kleen
2017-12-06 16:32 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2017-11-17 21:43 ` [PATCH v3 3/3] perf, tools, script: Allow computing metrics in perf script Andi Kleen
2017-11-20 9:04 ` Jiri Olsa
2017-11-20 15:35 ` Andi Kleen
2017-11-20 15:53 ` Jiri Olsa
2017-11-20 16:03 ` Andi Kleen
2017-11-21 9:28 ` Jiri Olsa
2017-11-21 17:07 ` Andi Kleen
2017-11-21 21:28 ` Jiri Olsa
2017-12-06 16:32 ` [tip:perf/core] perf script: Allow computing 'perf stat' style metrics tip-bot for Andi Kleen
2017-11-23 7:47 ` Add fine grained sampled metrics for perf script Jiri Olsa
2017-11-23 17:46 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-16 19:21 Andi Kleen
2017-11-09 14:55 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=20171123174617.GK8789@kernel.org \
--to=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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).