From: kan.liang@intel.com
To: acme@kernel.org
Cc: jolsa@kernel.org, a.p.zijlstra@chello.nl, mingo@redhat.com,
namhyung@kernel.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org, Kan Liang <kan.liang@intel.com>
Subject: [PATCH RFC 00/10] counter read during perf sampling
Date: Tue, 22 Sep 2015 10:13:33 -0400 [thread overview]
Message-ID: <1442931223-51708-1-git-send-email-kan.liang@intel.com> (raw)
From: Kan Liang <kan.liang@intel.com>
The patch series intends to read counter statistics with fixed frequency
during sampling. The instant benefit is that we can read memory bandwidth
from uncore event during cpu PMU event is sampling.
Introduce 'C' event/group modifier. The event with this modifier
will do counting not sampling. If a group with this modifier, only
group leader do sampling. The counter statistics will be wrote in
new RECORD type PERF_RECORD_COUNTER_READ and stored in perf.data.
So perf report can present the counter statistics data accordingly.
There may be an alternative way to get counter statistics during
sampling by running perf record and perf stat together by script.
But the script way have various issue and complex to parses the
output.
Example:
$perf record -e 'cycles,uncore_imc_1/cas_count_read/C'
--counter-read-interval 10 -a ./tchain_edit
[ perf record: Woken up 438 times to write data ]
[ perf record: Captured and wrote 1.232 MB perf.data (17901 samples) ]
$perf report -D
0x3cae0 [0x28]: PERF_RECORD_COUNTER_READ: uncore_imc_1/cas_count_read/C
CPU 0: val 1205 ena 2046148 run 2046148
0x3cb08 [0x28]: PERF_RECORD_COUNTER_READ: uncore_imc_1/cas_count_read/C
CPU 18: val 1315 ena 2001918 run 2001918
0x3dba0 [0x28]: PERF_RECORD_COUNTER_READ: uncore_imc_1/cas_count_read/C
CPU 0: val 1588 ena 12191520 run 12191520
0x3dbc8 [0x28]: PERF_RECORD_COUNTER_READ: uncore_imc_1/cas_count_read/C
CPU 18: val 1686 ena 12162202 run 12162202
$perf report --stdio --socket-filter 0
# To display the perf.data header info, please use --header/--header-only options.
#
#
# Total Lost Samples: 0
#
# Samples: 17K of event 'cycles'
# Event count (approx.): 10119095556
# Processor Socket: 0
#
# Overhead Command Shared Object Symbol
# ........ ............ ................... ..................................
#
97.68% tchain_edit tchain_edit [.] f3
0.07% tchain_edit tchain_edit [.] f2
0.04% swapper [kernel.vmlinux] [k] run_timer_softirq
0.04% swapper [kernel.vmlinux] [k] find_busiest_group
# Samples: 0 of event 'uncore_imc_1/cas_count_read/C'
# Event count (approx.): 0
# Processor Socket: 0
# uncore_imc_1/cas_count_read/C: 35937
Kan Liang (10):
perf,tools: Add 'C' event/group modifier
perf,tools: Enable counter statistic read for perf record
perf,tools: don't validate counter read event
perf,tools: New RECORD type PERF_RECORD_COUNTER_READ
perf,tools: record counter statistics during sampling
perf,tools: option to set counter read interval
perf,report: handle PERF_RECORD_COUNTER_READ
perf,tools: store counter val in events_stats
perf,tools: show counter read result in studio
perf,tools: show counter read result in tui browser title
tools/perf/Documentation/perf-list.txt | 5 ++
tools/perf/Documentation/perf-record.txt | 8 +++
tools/perf/builtin-record.c | 73 ++++++++++++++++++++++
tools/perf/builtin-report.c | 101 ++++++++++++++++++++++++++++++-
tools/perf/ui/browsers/hists.c | 37 +++++++++++
tools/perf/util/event.c | 1 +
tools/perf/util/event.h | 21 +++++++
tools/perf/util/evlist.c | 20 ++++++
tools/perf/util/evsel.c | 29 +++++++++
tools/perf/util/evsel.h | 1 +
tools/perf/util/parse-events.c | 8 ++-
tools/perf/util/parse-events.l | 2 +-
tools/perf/util/record.c | 6 +-
tools/perf/util/session.c | 16 +++++
tools/perf/util/tool.h | 1 +
15 files changed, 324 insertions(+), 5 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-09-22 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 14:13 kan.liang [this message]
2015-09-22 14:13 ` [PATCH RFC 01/10] perf,tools: Add 'C' event/group modifier kan.liang
2015-09-22 14:13 ` [PATCH RFC 02/10] perf,tools: Enable counter statistic read for perf record kan.liang
2015-09-22 14:13 ` [PATCH RFC 03/10] perf,tools: don't validate counter read event kan.liang
2015-09-22 14:13 ` [PATCH RFC 04/10] perf,tools: New RECORD type PERF_RECORD_COUNTER_READ kan.liang
2015-09-22 14:13 ` [PATCH RFC 05/10] perf,tools: record counter statistics during sampling kan.liang
2015-09-22 14:13 ` [PATCH RFC 06/10] perf,tools: option to set counter read interval kan.liang
2015-09-23 18:55 ` Sukadev Bhattiprolu
2015-09-23 19:07 ` Liang, Kan
2015-09-22 14:13 ` [PATCH RFC 07/10] perf,report: handle PERF_RECORD_COUNTER_READ kan.liang
2015-09-22 14:13 ` [PATCH RFC 08/10] perf,tools: store counter val in events_stats kan.liang
2015-09-22 14:13 ` [PATCH RFC 09/10] perf,tools: show counter read result in studio kan.liang
2015-09-22 14:13 ` [PATCH RFC 10/10] perf,tools: show counter read result in tui browser title kan.liang
2015-09-24 8:19 ` [PATCH RFC 00/10] counter read during perf sampling Jiri Olsa
2015-09-24 19:47 ` Liang, Kan
2015-09-24 22:28 ` Jiri Olsa
2015-09-25 14:57 ` Liang, Kan
2015-09-27 19:57 ` Jiri Olsa
2015-09-28 15:11 ` Liang, Kan
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=1442931223-51708-1-git-send-email-kan.liang@intel.com \
--to=kan.liang@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox