From: Jiri Olsa <jolsa@redhat.com>
To: ufo19890607 <ufo19890607@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
dsahern@gmail.com, namhyung@kernel.org, milian.wolff@kdab.com,
arnaldo.melo@gmail.com, yuzhoujian@didichuxing.com,
adrian.hunter@intel.com, wangnan0@huawei.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@redhat.com
Subject: Re: [PATCH 1/1] perf stat: Add support to print counts for fixed times
Date: Tue, 23 Jan 2018 15:24:50 +0100 [thread overview]
Message-ID: <20180123142449.GA21721@krava> (raw)
In-Reply-To: <1516192645-27187-2-git-send-email-ufo19890607@gmail.com>
On Wed, Jan 17, 2018 at 01:37:25PM +0100, ufo19890607 wrote:
> From: yuzhoujian <yuzhoujian@didichuxing.com>
>
> Introduce a new option to print counts for fixed number of times
> and update perf-stat documentation accordingly.
>
> Show below is the output of the new option for perf stat.
>
> $perf stat -I 1000 --times-print 2 -e cycles -a
> # time counts unit events
> 1.002827089 93,884,870 cycles
> 2.004231506 56,573,446 cycles
you can do that with following command:
[jolsa@krava perf]$ sudo ./perf stat -I 1000 -e cycles -a sleep 2
# time counts unit events
1.000160132 437,471,026 cycles
2.000367121 729,415,520 cycles
2.000857390 1,407,820 cycles
jirka
next prev parent reply other threads:[~2018-01-23 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 12:37 [PATCH 0/1] perf stat: Add support to print counts for fixed times ufo19890607
2018-01-17 12:37 ` [PATCH 1/1] " ufo19890607
2018-01-23 14:24 ` Jiri Olsa [this message]
[not found] ` <CAHCio2g-V-ojoi0igHSHNjj3ouzyhU+sO5WJSDHdZXGpUsZ7Ew@mail.gmail.com>
2018-01-24 7:39 ` Jiri Olsa
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=20180123142449.GA21721@krava \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ufo19890607@gmail.com \
--cc=wangnan0@huawei.com \
--cc=yuzhoujian@didichuxing.com \
/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).