From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v2 0/4] perf: Support a new 'percore' event qualifier
Date: Sun, 17 Mar 2019 00:34:24 +0800 [thread overview]
Message-ID: <1552754068-10325-1-git-send-email-yao.jin@linux.intel.com> (raw)
The 'percore' event qualifier which sums up the event counts for both
hardware threads in a core. For example,
perf stat -e cpu/event=0,umask=0x3,percore=1/,cpu/event=0,umask=0x3/
In this example, we count the event 'ref-cycles' per-core and per-CPU in
one perf stat command-line.
We can already support per-core counting with --per-core, but it's
often useful to do this together with other metrics that are collected
per CPU (per hardware thread). So this patch series supports this
per-core counting on a event level.
v2:
---
1. Change 'coresum' to 'percore'.
2. Move the aggregate counts printing to a seperate patch.
Jin Yao (4):
perf: Add a 'percore' event qualifier
perf stat: Factor out aggregate counts printing
perf stat: Support 'percore' event qualifier
perf test: Add a simple test for term 'percore'
tools/perf/Documentation/perf-stat.txt | 4 ++
tools/perf/builtin-stat.c | 21 +++++++
tools/perf/tests/parse-events.c | 10 ++-
tools/perf/util/evsel.c | 2 +
tools/perf/util/evsel.h | 3 +
tools/perf/util/parse-events.c | 27 +++++++++
tools/perf/util/parse-events.h | 1 +
tools/perf/util/parse-events.l | 1 +
tools/perf/util/stat-display.c | 108 ++++++++++++++++++++++++---------
tools/perf/util/stat.c | 8 ++-
10 files changed, 151 insertions(+), 34 deletions(-)
--
2.7.4
next reply other threads:[~2019-03-16 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 16:34 Jin Yao [this message]
2019-03-16 16:34 ` [PATCH v2 1/4] perf: Add a 'percore' event qualifier Jin Yao
2019-03-18 9:21 ` Jiri Olsa
2019-03-19 1:08 ` Jin, Yao
2019-03-16 16:34 ` [PATCH v2 2/4] perf stat: Factor out aggregate counts printing Jin Yao
2019-03-16 16:34 ` [PATCH v2 3/4] perf stat: Support 'percore' event qualifier Jin Yao
2019-03-16 16:34 ` [PATCH v2 4/4] perf test: Add a simple test for term 'percore' Jin Yao
2019-03-18 9:21 ` [PATCH v2 0/4] perf: Support a new 'percore' event qualifier 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=1552754068-10325-1-git-send-email-yao.jin@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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 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.