From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Stephane Eranian <eranian@google.com>,
Jin Yao <yao.jin@linux.intel.com>
Subject: Re: [PATCH v4] perf metricgroup: Fix uncore metric expressions
Date: Wed, 23 Sep 2020 17:25:08 -0300 [thread overview]
Message-ID: <20200923202508.GG2517482@kernel.org> (raw)
In-Reply-To: <CAP-5=fVJMeMhjwbO=ms7k0GsM6L1-uTdHqXUOJSvS4cr8M-Org@mail.gmail.com>
Em Wed, Sep 23, 2020 at 12:59:28PM -0700, Ian Rogers escreveu:
> On Thu, Sep 17, 2020 at 6:47 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > Hi Arnaldo,
> >
> > On Fri, Sep 18, 2020 at 5:39 AM Arnaldo Carvalho de Melo
> > <acme@kernel.org> wrote:
> > >
> > > Em Thu, Sep 17, 2020 at 01:18:07PM -0700, Ian Rogers escreveu:
> > > > A metric like DRAM_BW_Use has on SkylakeX events uncore_imc/cas_count_read/
> > > > and uncore_imc/case_count_write/. These events open 6 events per socket
> > > > with pmu names of uncore_imc_[0-5]. The current metric setup code in
> > > > find_evsel_group assumes one ID will map to 1 event to be recorded in
> > > > metric_events. For events with multiple matches, the first event is
> > > > recorded in metric_events (avoiding matching >1 event with the same
> > > > name) and the evlist_used updated so that duplicate events aren't
> > > > removed when the evlist has unused events removed.
> > >
> > > Namhyung, please check if you still Acks this as you provided it for v3.
> >
> > Sure,
> >
> > Acked-by: Namhyung Kim <namhyung@kernel.org>
>
> Thanks Namhyung and Arnaldo, could we merge this?
[acme@five perf]$ git log --oneline perf/urgent
dcc81be0fc4e6694 (quaco/perf/urgent, perf/urgent) perf metricgroup: Fix uncore metric expressions
0f1b550e29c1f952 perf parse-event: Release cpu_map refcount if evsel alloc failed
5d680be3b014d583 perf parse-event: Fix cpu map refcounting
5925fa68fe824465 (torvalds/master) Merge tag 'perf-tools-fixes-for-v5.9-2020-09-16' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
I have it already locally, need to finish a round of testing so that I
can push it publicly,
- Arnaldo
> Ian
>
> > Thanks
> > Namhyung
> >
> > >
> > > > Before this change:
> > > > $ /tmp/perf/perf stat -M DRAM_BW_Use -a -- sleep 1
> > > >
> > > > Performance counter stats for 'system wide':
> > > >
> > > > 41.14 MiB uncore_imc/cas_count_read/
> > > > 1,002,614,251 ns duration_time
> > > >
> > > > 1.002614251 seconds time elapsed
> > > >
> > > > After this change:
> > > > $ /tmp/perf/perf stat -M DRAM_BW_Use -a -- sleep 1
> > > >
> > > > Performance counter stats for 'system wide':
> > > >
> > > > 157.47 MiB uncore_imc/cas_count_read/ # 0.00 DRAM_BW_Use
> > > > 126.97 MiB uncore_imc/cas_count_write/
> > > > 1,003,019,728 ns duration_time
> > > >
> > > > Erroneous duplication introduced in:
> > > > commit 2440689d62e9 ("perf metricgroup: Remove duped metric group events").
> > > >
> > > > Fixes: ded80bda8bc9 ("perf expr: Migrate expr ids table to a hashmap").
> > > > Reported-by: Jin Yao <yao.jin@linux.intel.com>
> > > > Signed-off-by: Ian Rogers <irogers@google.com>
> > > > ---
> > > > tools/perf/util/metricgroup.c | 75 ++++++++++++++++++++++++++---------
> > > > 1 file changed, 56 insertions(+), 19 deletions(-)
> > > >
> > > > diff --git a/tools/perf/util/metricgroup.c b/tools/perf/util/metricgroup.c
> > > > index ab5030fcfed4..d948a7f910cf 100644
> > > > --- a/tools/perf/util/metricgroup.c
> > > > +++ b/tools/perf/util/metricgroup.c
> > > > @@ -150,6 +150,18 @@ static void expr_ids__exit(struct expr_ids *ids)
> > > > free(ids->id[i].id);
> > > > }
> > > >
> > > > +static bool contains_event(struct evsel **metric_events, int num_events,
> > > > + const char *event_name)
> > > > +{
> > > > + int i;
> > > > +
> > > > + for (i = 0; i < num_events; i++) {
> > > > + if (!strcmp(metric_events[i]->name, event_name))
> > > > + return true;
> > > > + }
> > > > + return false;
> > > > +}
> > > > +
> > > > /**
> > > > * Find a group of events in perf_evlist that correpond to those from a parsed
> > > > * metric expression. Note, as find_evsel_group is called in the same order as
> > > > @@ -180,7 +192,11 @@ static struct evsel *find_evsel_group(struct evlist *perf_evlist,
> > > > int i = 0, matched_events = 0, events_to_match;
> > > > const int idnum = (int)hashmap__size(&pctx->ids);
> > > >
> > > > - /* duration_time is grouped separately. */
> > > > + /*
> > > > + * duration_time is always grouped separately, when events are grouped
> > > > + * (ie has_constraint is false) then ignore it in the matching loop and
> > > > + * add it to metric_events at the end.
> > > > + */
> > > > if (!has_constraint &&
> > > > hashmap__find(&pctx->ids, "duration_time", (void **)&val_ptr))
> > > > events_to_match = idnum - 1;
> > > > @@ -207,23 +223,20 @@ static struct evsel *find_evsel_group(struct evlist *perf_evlist,
> > > > sizeof(struct evsel *) * idnum);
> > > > current_leader = ev->leader;
> > > > }
> > > > - if (hashmap__find(&pctx->ids, ev->name, (void **)&val_ptr)) {
> > > > - if (has_constraint) {
> > > > - /*
> > > > - * Events aren't grouped, ensure the same event
> > > > - * isn't matched from two groups.
> > > > - */
> > > > - for (i = 0; i < matched_events; i++) {
> > > > - if (!strcmp(ev->name,
> > > > - metric_events[i]->name)) {
> > > > - break;
> > > > - }
> > > > - }
> > > > - if (i != matched_events)
> > > > - continue;
> > > > - }
> > > > + /*
> > > > + * Check for duplicate events with the same name. For example,
> > > > + * uncore_imc/cas_count_read/ will turn into 6 events per socket
> > > > + * on skylakex. Only the first such event is placed in
> > > > + * metric_events. If events aren't grouped then this also
> > > > + * ensures that the same event in different sibling groups
> > > > + * aren't both added to metric_events.
> > > > + */
> > > > + if (contains_event(metric_events, matched_events, ev->name))
> > > > + continue;
> > > > + /* Does this event belong to the parse context? */
> > > > + if (hashmap__find(&pctx->ids, ev->name, (void **)&val_ptr))
> > > > metric_events[matched_events++] = ev;
> > > > - }
> > > > +
> > > > if (matched_events == events_to_match)
> > > > break;
> > > > }
> > > > @@ -239,7 +252,7 @@ static struct evsel *find_evsel_group(struct evlist *perf_evlist,
> > > > }
> > > >
> > > > if (matched_events != idnum) {
> > > > - /* Not whole match */
> > > > + /* Not a whole match */
> > > > return NULL;
> > > > }
> > > >
> > > > @@ -247,8 +260,32 @@ static struct evsel *find_evsel_group(struct evlist *perf_evlist,
> > > >
> > > > for (i = 0; i < idnum; i++) {
> > > > ev = metric_events[i];
> > > > - ev->metric_leader = ev;
> > > > + /* Don't free the used events. */
> > > > set_bit(ev->idx, evlist_used);
> > > > + /*
> > > > + * The metric leader points to the identically named event in
> > > > + * metric_events.
> > > > + */
> > > > + ev->metric_leader = ev;
> > > > + /*
> > > > + * Mark two events with identical names in the same group (or
> > > > + * globally) as being in use as uncore events may be duplicated
> > > > + * for each pmu. Set the metric leader of such events to be the
> > > > + * event that appears in metric_events.
> > > > + */
> > > > + evlist__for_each_entry_continue(perf_evlist, ev) {
> > > > + /*
> > > > + * If events are grouped then the search can terminate
> > > > + * when then group is left.
> > > > + */
> > > > + if (!has_constraint &&
> > > > + ev->leader != metric_events[i]->leader)
> > > > + break;
> > > > + if (!strcmp(metric_events[i]->name, ev->name)) {
> > > > + set_bit(ev->idx, evlist_used);
> > > > + ev->metric_leader = metric_events[i];
> > > > + }
> > > > + }
> > > > }
> > > >
> > > > return metric_events[0];
> > > > --
> > > > 2.28.0.618.gf4bc123cb7-goog
> > > >
> > >
> > > --
> > >
> > > - Arnaldo
--
- Arnaldo
prev parent reply other threads:[~2020-09-23 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200917190026.GB1426933@kernel.org>
2020-09-17 20:18 ` [PATCH v4] perf metricgroup: Fix uncore metric expressions Ian Rogers
2020-09-17 20:39 ` Arnaldo Carvalho de Melo
2020-09-18 1:47 ` Namhyung Kim
2020-09-23 19:59 ` Ian Rogers
2020-09-23 20:25 ` Arnaldo Carvalho de Melo [this message]
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=20200923202508.GG2517482@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=yao.jin@linux.intel.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).