From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v3 1/4] perf: Add a 'percore' event qualifier
Date: Wed, 10 Apr 2019 09:54:31 -0300 [thread overview]
Message-ID: <20190410125431.GC13888@kernel.org> (raw)
In-Reply-To: <20190410123641.GA13888@kernel.org>
Em Wed, Apr 10, 2019 at 09:36:41AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Mar 19, 2019 at 04:56:53PM +0800, Jin Yao escreveu:
> > Add a 'percore' event qualifier, like cpu/event=0,umask=0x3,percore=1/,
> > that sums up the event counts for both hardware threads in a core.
> >
> > We can already do this with --per-core, but it's often useful to do
> > this together with other metrics that are collected per hardware thread.
> > So we need to support this per-core counting on a event level.
> >
> > This can be implemented in only the user tool, no kernel support needed.
> >
> > v3:
> > ---
> > Simplify the code according to Jiri's comments.
> > Before:
> > "return term->val.percore ? true : false;"
> > Now:
> > "return term->val.percore;"
> >
> > v2:
> > ---
> > Change the qualifier name from 'coresum' to 'percore' according to
> > comments from Jiri and Andi.
>
> I'm applying this, but please, don't forget to, when adding a new
> qualifier, to update the documentation... I'm doing this for you this
> time.
The first patch didn't apply with 'git am', I did it manually, and added
the patch below
But then the second doesn't apply to my perf/core branch as well, please
refresh and resend a v4, thanks.
- Arnaldo
diff --git a/tools/perf/Documentation/perf-list.txt b/tools/perf/Documentation/perf-list.txt
index 138fb6e94b3c..18ed1b0fceb3 100644
--- a/tools/perf/Documentation/perf-list.txt
+++ b/tools/perf/Documentation/perf-list.txt
@@ -199,6 +199,18 @@ also be supplied. For example:
perf stat -C 0 -e 'hv_gpci/dtbp_ptitc,phys_processor_idx=0x2/' ...
+EVENT QUALIFIERS:
+
+It is also possible to add extra qualifiers to an event:
+
+percore:
+
+Sums up the event counts for all hardware threads in a core, e.g.:
+
+
+ perf stat -e cpu/event=0,umask=0x3,percore=1/
+
+
EVENT GROUPS
------------
next prev parent reply other threads:[~2019-04-10 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 8:56 [PATCH v3 0/4] perf: Support a new 'percore' event qualifier Jin Yao
2019-03-19 8:56 ` [PATCH v3 1/4] perf: Add a " Jin Yao
2019-04-10 12:36 ` Arnaldo Carvalho de Melo
2019-04-10 12:54 ` Arnaldo Carvalho de Melo [this message]
2019-04-10 14:15 ` Jin, Yao
2019-03-19 8:56 ` [PATCH v3 2/4] perf stat: Factor out aggregate counts printing Jin Yao
2019-03-19 8:56 ` [PATCH v3 3/4] perf stat: Support 'percore' event qualifier Jin Yao
2019-03-19 8:56 ` [PATCH v3 4/4] perf test: Add a simple test for term 'percore' Jin Yao
2019-03-19 10:20 ` [PATCH v3 0/4] perf: Support a new 'percore' event qualifier Jiri Olsa
2019-04-10 2:32 ` Jin, Yao
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=20190410125431.GC13888@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=Linux-kernel@vger.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 \
--cc=yao.jin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox