All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Xing Zhengjun <zhengjun.xing@linux.intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	perry.taylor@intel.com, caleb.biggers@intel.com,
	kshipra.bopardikar@intel.com, samantha.alt@intel.com,
	ahmad.yasin@intel.com, 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@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	John Garry <john.garry@huawei.com>,
	James Clark <james.clark@arm.com>,
	Kajol Jain <kjain@linux.ibm.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Miaoqian Lin <linmq006@gmail.com>,
	Florian Fischer <florian.fischer@muhq.space>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v1 05/22] perf vendor events: Update Intel alderlake
Date: Thu, 29 Sep 2022 10:00:52 -0300	[thread overview]
Message-ID: <YzWXBGyjs39cD7Cd@kernel.org> (raw)
In-Reply-To: <CAP-5=fUogKZx6JP_vg+6ti+BnbEcX+3Wnzi077s4VgxEKLpQeQ@mail.gmail.com>

Em Wed, Sep 28, 2022 at 07:23:37PM -0700, Ian Rogers escreveu:
> On Wed, Sep 28, 2022 at 7:08 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > Em Wed, Sep 28, 2022 at 04:22:53PM +0800, Xing Zhengjun escreveu:
> > > On 9/28/2022 3:21 PM, Ian Rogers wrote:
> > > > diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
> > > > index 7f2d777fd97f..594c6e96f0ce 100644
> > > > --- a/tools/perf/pmu-events/arch/x86/mapfile.csv
> > > > +++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
> > > > @@ -1,5 +1,5 @@
> > > >   Family-model,Version,Filename,EventType
> > > > -GenuineIntel-6-9[7A],v1.13,alderlake,core
> > > > +GenuineIntel-6-(97|9A|B7|BA|BF),v1.15,alderlake,core
> > >
> > > The commit description should mention this change "Add more CPUID support
> > > for ADL"
> >
> > I added this note, with that can I have your Reviewed-by or Acked-by?
> >
> > - Arnaldo
> 
> I think I should send a v2. I can add this then. Other things for v2 are:

Ok, I'll drop v1 from my local, testing branch.

> - this week there will likely be an update to [1] which is implicitly
> integrated here.
> - the topdown metrics are all percentages but are currently values
> zero to 1. It is straightforward to add a ScaleUnit of 100% to them
> all.
> - eyeballing topdown event metrics like:
> 
>     {
>        "BriefDescription": "This category represents fraction of slots
> utilized by useful work i.e. issued uops that eventually get retired",
>        "MetricExpr": "topdown\\-retiring / (topdown\\-fe\\-bound +
> topdown\\-bad\\-spec + topdown\\-retiring + topdown\\-be\\-bound)",
>        "MetricGroup": "TopdownL1;tma_L1_group",
>        "MetricName": "tma_retiring",
> ...
> it looks like the group will fail due to the missing slots event. This
> can be fixed with:
>        "MetricExpr": "topdown\\-retiring / (topdown\\-fe\\-bound +
> topdown\\-bad\\-spec + topdown\\-retiring + topdown\\-be\\-bound) + 0
> * TOPDOWN.SLOTS",
> 
> Thanks,
> Ian
> 
> [1] https://github.com/intel/perfmon-metrics
> 
> > > >   GenuineIntel-6-(1C|26|27|35|36),v4,bonnell,core
> > > >   GenuineIntel-6-(3D|47),v26,broadwell,core
> > > >   GenuineIntel-6-56,v23,broadwellde,core
> > >
> > > --
> > > Zhengjun Xing
> >
> > --
> >
> > - Arnaldo

-- 

- Arnaldo

  parent reply	other threads:[~2022-09-29 13:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  7:21 [PATCH v1 00/22] Improvements to Intel perf metrics Ian Rogers
2022-09-28  7:21 ` [PATCH v1 01/22] perf expr: Allow a double if expression Ian Rogers
2022-09-28  7:21 ` [PATCH v1 02/22] perf expr: Remove jevents case workaround Ian Rogers
2022-09-28  7:21 ` [PATCH v1 03/22] perf metrics: Don't scale counts going into metrics Ian Rogers
2022-09-29  8:48   ` Xing Zhengjun
2022-10-04  1:34     ` Ian Rogers
2022-09-28  7:21 ` [PATCH v1 04/22] perf vendor events: Update Intel skylakex Ian Rogers
2022-09-28  7:21 ` [PATCH v1 05/22] perf vendor events: Update Intel alderlake Ian Rogers
2022-09-28  8:22   ` Xing Zhengjun
2022-09-28 14:07     ` Arnaldo Carvalho de Melo
2022-09-29  2:23       ` Ian Rogers
2022-09-29  8:12         ` Xing Zhengjun
2022-09-29 13:00         ` Arnaldo Carvalho de Melo [this message]
2022-09-28  7:21 ` [PATCH v1 06/22] perf vendor events: Update Intel broadwell Ian Rogers
2022-09-28  7:21 ` [PATCH v1 07/22] perf vendor events: Update Intel broadwellx Ian Rogers
2022-09-28  7:21 ` [PATCH v1 08/22] perf vendor events: Update Intel cascadelakex Ian Rogers
2022-09-28  7:21 ` [PATCH v1 09/22] perf vendor events: Update elkhartlake cpuids Ian Rogers
2022-09-28  7:21 ` [PATCH v1 10/22] perf vendor events: Update Intel haswell Ian Rogers
2022-09-28  7:21 ` [PATCH v1 11/22] perf vendor events: Update Intel haswellx Ian Rogers
2022-09-28  7:21 ` [PATCH v1 12/22] perf vendor events: Update Intel icelake Ian Rogers
2022-09-28  7:21 ` [PATCH v1 13/22] perf vendor events: Update Intel icelakex Ian Rogers
2022-09-28  7:21 ` [PATCH v1 14/22] perf vendor events: Update Intel ivybridge Ian Rogers
2022-09-28  7:21 ` [PATCH v1 15/22] perf vendor events: Update Intel ivytown Ian Rogers
2022-09-28  7:21 ` [PATCH v1 16/22] perf vendor events: Update Intel jaketown Ian Rogers
2022-09-28  7:21 ` [PATCH v1 17/22] perf vendor events: Update Intel sandybridge Ian Rogers
2022-09-28  7:22 ` [PATCH v1 18/22] perf vendor events: Update Intel sapphirerapids Ian Rogers
2022-09-28  7:22 ` [PATCH v1 19/22] perf vendor events: Update silvermont cpuids Ian Rogers
2022-09-28  7:22 ` [PATCH v1 20/22] perf vendor events: Update Intel skylake Ian Rogers
2022-09-28  7:22 ` [PATCH v1 21/22] perf vendor events: Update Intel tigerlake Ian Rogers
2022-09-28  7:22 ` [PATCH v1 22/22] perf vendor events: Update Intel broadwellde Ian Rogers
2022-09-28 12:56 ` [PATCH v1 00/22] Improvements to Intel perf metrics Liang, Kan
2022-09-28 14:04   ` Ian Rogers
2022-09-28 15:05     ` 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=YzWXBGyjs39cD7Cd@kernel.org \
    --to=acme@kernel.org \
    --cc=ahmad.yasin@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=caleb.biggers@intel.com \
    --cc=eranian@google.com \
    --cc=florian.fischer@muhq.space \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kjain@linux.ibm.com \
    --cc=kshipra.bopardikar@intel.com \
    --cc=linmq006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=perry.taylor@intel.com \
    --cc=peterz@infradead.org \
    --cc=samantha.alt@intel.com \
    --cc=tmricht@linux.ibm.com \
    --cc=zhengjun.xing@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.