From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: kan.liang@linux.intel.com, acme@kernel.org, jolsa@kernel.org,
adrian.hunter@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, "Khalil,
Amiri" <amiri.khalil@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] perf stat: Fix the hard-coded metrics calculation on the hybrid
Date: Thu, 6 Jun 2024 00:34:17 -0700 [thread overview]
Message-ID: <CAM9d7cjuHYDMvcq10ZD=3LSmia4WcvAzsme89B-odHYBAZzWYg@mail.gmail.com> (raw)
In-Reply-To: <CAP-5=fV+-ytA2st17Ar-jQ5xYqrWtxnF2TcADKrC5WoPyKz4wQ@mail.gmail.com>
On Wed, Jun 5, 2024 at 10:21 AM Ian Rogers <irogers@google.com> wrote:
>
> On Wed, Jun 5, 2024 at 9:10 AM <kan.liang@linux.intel.com> wrote:
> >
> > From: Kan Liang <kan.liang@linux.intel.com>
> >
> > The hard-coded metrics is wrongly calculated on the hybrid machine.
> >
> > $ perf stat -e cycles,instructions -a sleep 1
> >
> > Performance counter stats for 'system wide':
> >
> > 18,205,487 cpu_atom/cycles/
> > 9,733,603 cpu_core/cycles/
> > 9,423,111 cpu_atom/instructions/ # 0.52 insn per cycle
> > 4,268,965 cpu_core/instructions/ # 0.23 insn per cycle
> >
> > The insn per cycle for cpu_core should be 4,268,965 / 9,733,603 = 0.44.
> >
> > When finding the metric events, the find_stat() doesn't take the PMU
> > type into account. The cpu_atom/cycles/ is wrongly used to calculate
> > the IPC of the cpu_core.
> >
> > Fixes: 0a57b910807a ("perf stat: Use counts rather than saved_value")
> > Reported-by: "Khalil, Amiri" <amiri.khalil@intel.com>
> > Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
>
> Thanks,
> Ian
>
> > Cc: stable@vger.kernel.org
> > ---
> > tools/perf/util/stat-shadow.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/tools/perf/util/stat-shadow.c b/tools/perf/util/stat-shadow.c
> > index 3466aa952442..4d0edc061f1a 100644
> > --- a/tools/perf/util/stat-shadow.c
> > +++ b/tools/perf/util/stat-shadow.c
> > @@ -176,6 +176,10 @@ static double find_stat(const struct evsel *evsel, int aggr_idx, enum stat_type
> > if (type != evsel__stat_type(cur))
> > continue;
> >
> > + /* Ignore if not the PMU we're looking for. */
> > + if (evsel->pmu != cur->pmu)
> > + continue;
Hmm.. Don't some metrics need events from different PMU?
Like cycles per sec or branch instructions per sec..
Thanks,
Namhyung
> > +
> > aggr = &cur->stats->aggr[aggr_idx];
> > if (type == STAT_NSECS)
> > return aggr->counts.val;
> > --
> > 2.35.1
> >
next prev parent reply other threads:[~2024-06-06 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 16:08 [PATCH] perf stat: Fix the hard-coded metrics calculation on the hybrid kan.liang
2024-06-05 17:21 ` Ian Rogers
2024-06-06 7:34 ` Namhyung Kim [this message]
2024-06-06 13:44 ` Liang, Kan
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='CAM9d7cjuHYDMvcq10ZD=3LSmia4WcvAzsme89B-odHYBAZzWYg@mail.gmail.com' \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=amiri.khalil@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).