All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@elte.hu, ak@linux.intel.com, acme@redhat.com,
	jolsa@redhat.com, namhyung.kim@lge.com
Subject: Re: [PATCH v6 2/2] perf stat: add interval printing
Date: Thu, 24 Jan 2013 10:39:07 +0100	[thread overview]
Message-ID: <20130124093907.GA24621@gmail.com> (raw)
In-Reply-To: <1358860732-4435-3-git-send-email-eranian@google.com>


* Stephane Eranian <eranian@google.com> wrote:

> This patch adds a new printing mode for perf stat.
> It allows internval printing. That means perf stat

s/rnv/rv

> can now print event deltas at regular time interval.
> This is useful to detect phases in programs.
> 
> The -I option enables interval printing. It expects
> an interval duration in milliseconds. Minimum is
> 100ms. Once, activated perf stat prints events deltas
> since last printout. All modes are supported.
> 
> $ perf stat -I 1000 -e cycles noploop 10
> noploop for 10 seconds
>  #           time             counts events
>       1.000109853      2,388,560,546 cycles
>       2.000262846      2,393,332,358 cycles
>       3.000354131      2,393,176,537 cycles
>       4.000439503      2,393,203,790 cycles
>       5.000527075      2,393,167,675 cycles
>       6.000609052      2,393,203,670 cycles
>       7.000691082      2,393,175,678 cycles

Looks useful!

Thanks,

	Ingo

  reply	other threads:[~2013-01-24  9:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 13:18 [PATCH v6 0/2] perf stat: add interval counter printing Stephane Eranian
2013-01-22 13:18 ` [PATCH v6 1/2] perf tools: add evsel prev_raw_count field Stephane Eranian
2013-01-22 13:18 ` [PATCH v6 2/2] perf stat: add interval printing Stephane Eranian
2013-01-24  9:39   ` Ingo Molnar [this message]
2013-01-25  2:52   ` Arnaldo Carvalho de Melo
2013-01-25 15:21     ` Stephane Eranian
2013-01-28 17:59       ` Arnaldo Carvalho de Melo
2013-01-28 18:26         ` Stephane Eranian
2013-01-28 19:21           ` Arnaldo Carvalho de Melo
2013-01-28 22:45             ` Stephane Eranian
2013-01-29  1:41               ` Arnaldo Carvalho de Melo
2013-01-29 11:48                 ` Stephane Eranian
2013-01-29 20:58                   ` Arnaldo Carvalho de Melo

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=20130124093907.GA24621@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.