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>, Kajol Jain <kjain@linux.ibm.com>,
Kan Liang <kan.liang@linux.intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v3] perf metricgroup: Fix uncore metric expressions
Date: Thu, 17 Sep 2020 16:00:26 -0300 [thread overview]
Message-ID: <20200917190026.GB1426933@kernel.org> (raw)
In-Reply-To: <CAM9d7cjLpE=cKfemsuokc57-5kzezRr3YzqOKZb9Pf4r4-X8+g@mail.gmail.com>
Em Fri, Sep 11, 2020 at 12:07:35PM +0900, Namhyung Kim escreveu:
> On Fri, Sep 11, 2020 at 3:02 AM Ian Rogers <irogers@google.com> wrote:
> > v3. cleans up searching for the same event within metric_events to use a
> > helper and avoids a redundant search. It uses a continue loop to
> > make the search for similarly named events shorter.
> > v2. avoids iterating over the whole evlist as suggested by
> > namhyung@kernel.org. It also fixes the metric_leader computation
> > that was broken in the same commits.
> >
> > 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>
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
On my perf/urgent branch (upstream should be the same):
[acme@five perf]$ patch -p1 < /wb/1.patch
patching file tools/perf/util/metricgroup.c
Hunk #1 succeeded at 150 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 192 (offset 1 line).
Hunk #3 succeeded at 223 (offset 1 line).
Hunk #4 succeeded at 252 (offset 1 line).
Hunk #5 succeeded at 260 (offset 1 line).
[acme@five perf]$
I'm fixing it up, please check that doing this is safe on your side.
- Arnaldo
next prev parent reply other threads:[~2020-09-17 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 18:02 [PATCH v3] perf metricgroup: Fix uncore metric expressions Ian Rogers
2020-09-11 3:07 ` Namhyung Kim
2020-09-17 19:00 ` Arnaldo Carvalho de Melo [this message]
2020-09-17 20:18 ` [PATCH v4] " 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
2020-09-17 20:20 ` [PATCH v3] " Ian Rogers
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=20200917190026.GB1426933@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.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 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.