linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	Kan.liang@intel.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org, acme@redhat.com
Subject: Re: [PATCH v4 0/2] perf stat: Add interval-count and time support
Date: Mon, 29 Jan 2018 11:25:58 +0100	[thread overview]
Message-ID: <20180129102558.GA14925@krava> (raw)
In-Reply-To: <1517217923-8302-1-git-send-email-ufo19890607@gmail.com>

On Mon, Jan 29, 2018 at 10:25:21AM +0100, ufo19890607 wrote:
> From: yuzhoujian <yuzhoujian@didichuxing.com>
> 
> Introduce two new options for perf stat and update perf-stat documentation
> accordingly.
> 
> The interval-count option can be used to print counts for fixed number of
> times, and it should be used specifically with "-I" option.
> 
> Show below is the output of the interval-count option for perf stat.
> 
>         $ perf stat -I 1000 --interval-count 2 -e cycles -a
>         #           time             counts unit events
>              1.002827089         93,884,870      cycles
>              2.004231506         56,573,446      cycles
>     
> The time option can be used to print counts after a period of time, and it
> should not be used with "-I" option.
> 
> Show below is the output of the time option for perf stat.
> 
>         $ perf stat --time 2000 -e cycles -a
>         Performance counter stats for 'system wide':
> 
>                 157,260,423      cycles
> 
>                 2.003060766 seconds time elapsed
> 
> yuzhoujian (2):
>   perf stat: Add support to print counts for fixed times
>   perf stat: Add support to print counts after a period of time
> 
> Changes since v3: 
> - merge interval_count check and times check to one line.
> - fix the wrong indent in stat.h
> - use stat_config.times instead of 'times' in cmd_stat function.

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

> 
> Changes since v2: 
> - modify the time check in __run_perf_stat func to keep some consistency
>   with the workload case.
> - add the warning when the time is set between 10ms to 100ms.
> - add the pr_err when the time is set below 10ms.
> 
> Changes since v1:
> - change the name of the new option "times-print" to "interval-count".
> - keep the interval-count option interval specifically.
> 
> 
>  tools/perf/Documentation/perf-stat.txt | 10 +++++++
>  tools/perf/builtin-stat.c              | 53 ++++++++++++++++++++++++++++++++--
>  tools/perf/util/stat.h                 |  2 ++
>  3 files changed, 62 insertions(+), 3 deletions(-)
> 
> -- 
> 2.14.1
> 

  parent reply	other threads:[~2018-01-29 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29  9:25 [PATCH v4 0/2] perf stat: Add interval-count and time support ufo19890607
2018-01-29  9:25 ` [PATCH v4 1/2] perf stat: Add support to print counts for fixed times ufo19890607
2018-01-29  9:25 ` [PATCH v4 2/2] perf stat: Add support to print counts after a period of time ufo19890607
2018-02-15 13:39   ` Arnaldo Carvalho de Melo
2018-02-16 13:18     ` Arnaldo Carvalho de Melo
2018-01-29 10:25 ` Jiri Olsa [this message]
     [not found]   ` <CAHCio2iVBoEXEv3mXzq34FsDZXJT9Oig+SfDwv3vneYfZQ089g@mail.gmail.com>
2018-02-15 10:44     ` [PATCH v4 0/2] perf stat: Add interval-count and time support 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=20180129102558.GA14925@krava \
    --to=jolsa@redhat.com \
    --cc=Kan.liang@intel.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).