From: Jiri Olsa <jolsa@redhat.com>
To: Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] perf stat: enable 1ms interval for printing event counters values
Date: Wed, 4 Apr 2018 09:05:16 +0200 [thread overview]
Message-ID: <20180404070516.GB2313@krava> (raw)
In-Reply-To: <b842ad6a-d606-32e4-afe5-974071b5198e@linux.intel.com>
On Tue, Apr 03, 2018 at 09:18:33PM +0300, Alexey Budankov wrote:
>
> Currently print count interval for performance counters values is
> limited by 10ms so reading the values at frequencies higher than 100Hz
> is restricted by the tool.
>
> This change makes perf stat -I possible on frequencies up to 1KHz and,
> to some extent, makes perf stat -I to be on-par with perf record
> sampling profiling.
>
> When running perf stat -I for monitoring e.g. PCIe uncore counters and
> at the same time profiling some I/O workload by perf record e.g. for
> cpu-cycles and context switches, it is then possible to observe
> consolidated CPU/OS/IO(Uncore) performance picture for that workload.
>
> Tool overhead warning printed when specifying -v option can be missed
> due to screen scrolling in case you have output to the console
> so message is moved into help available by running perf stat -h.
>
> Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
> ---
>
> Changes in v2:
> - updated minimum value to 1ms at perf-stat.txt manual
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2018-04-04 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 18:18 [PATCH v2] perf stat: enable 1ms interval for printing event counters values Alexey Budankov
2018-04-04 7:05 ` Jiri Olsa [this message]
2018-04-04 13:39 ` Arnaldo Carvalho de Melo
2018-04-16 6:40 ` [tip:perf/urgent] perf stat: Enable " tip-bot for Alexey Budankov
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=20180404070516.GB2313@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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.