[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <660a0c4f-cecd-df97-3fea-3d75d45fa02b@huawei.com>
Date: Mon, 17 Jan 2022 18:04:01 +0000
From: John Garry <john.garry@...wei.com>
To: Ian Rogers <irogers@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
"Namhyung Kim" <namhyung@...nel.org>,
Andi Kleen <ak@...ux.intel.com>,
<linux-perf-users@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: <eranian@...gle.com>
Subject: Re: [PATCH] perf metric: Fix metric_leader
On 15/01/2022 06:28, Ian Rogers wrote:
> Multiple events may have a metric_leader to aggregate into. This happens
> for uncore events where, for example, uncore_imc is expanded into
> uncore_imc_0, uncore_imc_1, etc. Such events all have the same metric_id
> and should aggregate into the first event. The change introducing
> metric_ids had a bug where the metric_id was compared to itself,
> creating an always true condition. Correct this by comparing the
> event in the metric_evlist and the metric_leader.
>
> Fixes: ec5c5b3d2c21 ("perf metric: Encode and use metric-id as qualifier")
> Signed-off-by: Ian Rogers<irogers@...gle.com>
> ---
Looks ok and I quickly tested it:
Reviewed-by: John Garry <john.garry@...wei.com>
Powered by blists - more mailing lists