From: Jiri Olsa <jolsa@redhat.com>
To: 禹舟键 <ufo19890607@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@redhat.com,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Milian Wolff <milian.wolff@kdab.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Wind Yu <yuzhoujian@didichuxing.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Wang Nan <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: Wed, 24 Jan 2018 08:39:18 +0100 [thread overview]
Message-ID: <20180124073918.GB8473@krava> (raw)
In-Reply-To: <CAHCio2g-V-ojoi0igHSHNjj3ouzyhU+sO5WJSDHdZXGpUsZ7Ew@mail.gmail.com>
On Wed, Jan 24, 2018 at 10:03:08AM +0800, 禹舟键 wrote:
> Hi Jirka
> How can you control the output for perf stat, if the "--interval-print" is
> not 1000, eg. 2000, 3000, 5000.
>
> root@node10:/home$ ./perf stat -e cycles -a -I 2000 sleep 3
> # time counts unit events
> 2.001361101 695,569,361 cycles
> 3.003249250 57,904,006 cycles
> root@node10:/home$ ./perf stat -e cycles -a -I 2000 --times-print 3
> # time counts unit events
> 2.002784924 128,438,406
> cycles
> 4.004290885 93,128,097
> cycles
> 6.005726281 111,303,359 cycles
[jolsa@krava perf]$ sudo ./perf stat -e cycles -a -I 2000 --times-print 3
# time counts unit events
2.000161257 1,197,889,478 cycles
4.000424645 2,905,635,530 cycles
6.000589943 1,658,546,001 cycles
[jolsa@krava perf]$ sudo ./perf stat -e cycles -a -I 2000 sleep 6
# time counts unit events
2.000248489 1,224,257,116 cycles
4.000489261 3,171,435,328 cycles
6.000766440 4,092,029,501 cycles
6.916537222 563,745,072 cycles
jirka
prev parent reply other threads:[~2018-01-24 7:39 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
[not found] ` <CAHCio2g-V-ojoi0igHSHNjj3ouzyhU+sO5WJSDHdZXGpUsZ7Ew@mail.gmail.com>
2018-01-24 7:39 ` Jiri Olsa [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=20180124073918.GB8473@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).