The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "Baker, Edward" <edward.baker@intel.com>,
	"alexander.shishkin@linux.intel.com"
	<alexander.shishkin@linux.intel.com>,
	"Biggers, Caleb" <caleb.biggers@intel.com>,
	"mpetlan@redhat.com" <mpetlan@redhat.com>,
	"Taylor, Perry" <perry.taylor@intel.com>,
	"Hunter, Adrian" <adrian.hunter@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"irogers@google.com" <irogers@google.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
	"manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"Alt, Samantha" <samantha.alt@intel.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"Wang, Weilin" <weilin.wang@intel.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"afaerber@suse.de" <afaerber@suse.de>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [PATCH v4 00/23] Intel vendor events and TMA 5.01 metrics
Date: Wed, 5 Feb 2025 04:28:17 +0000	[thread overview]
Message-ID: <d44036481022c27d83ce0faf8c7f77042baedb34.camel@intel.com> (raw)
In-Reply-To: <CAP-5=fXpuND+kNe16CJMETkMOW+__eQpB8No0ra5gyEcfqCCKQ@mail.gmail.com>

On Tue, 2025-02-04 at 13:35 -0800, Ian Rogers wrote:
> On Tue, Feb 4, 2025 at 1:33 PM Ian Rogers <irogers@google.com> wrote:
> > 
> > Update the Intel vendor events to the latest.
> > Update the metrics to TMA 5.01.
> > Add Arrowlake and Clearwaterforest support.
> > Add metrics for LNL and GNR.
> > Address IIO uncore issue spotted on EMR, GRR, GNR, SPR and SRF.
> > 
> > The perf json was generated using the script:
> > https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> > with the generated json being in:
> > https://github.com/intel/perfmon/tree/main/scripts/perf
> > 
> > Thanks to Perry Taylor <perry.taylor@intel.com>, Caleb Biggers
> > <caleb.biggers@intel.com>, Edward Baker <edward.baker@intel.com>
> > and
> > Weilin Wang <weilin.wang@intel.com> for helping get this patch
> > series
> > together.
> > 
> > v4: Fix TSC events on hybrid mistakenly specifying the core PMU
> >     inhibiting the use of the msr PMU.
> > v3: Fixes for hybrid metrics that were missing PMU. Update to the
> >     latest events.
> > v2: Fix hybrid and Co-authored-by tag issues reported by
> >     Arnaldo. Updates to Lunarlake and Meteorlake events. Addition
> > of
> >     Clearwaterforest.
> 
> Sorry, forgot to add Thomas again.
> https://lore.kernel.org/lkml/20250204213259.127939-1-irogers@google.com/

Hi, I'm seeing some warnings like this and the all metrics test is
skipped:

Testing tma_info_inst_mix_iparith
FP issues
Cannot resolve IDs for tma_info_inst_mix_iparith:
cpu_core@INST_RETIRED.ANY@ / (cpu_core@FP_ARITH_INST_RETIRED.SCALAR@ +
cpu_core@FP_ARITH_INST_RETIRED.VECTOR@)
Testing tma_info_inst_mix_iparith_avx128
FP issues
Cannot resolve IDs for tma_info_inst_mix_iparith_avx128:
cpu_core@INST_RETIRED.ANY@ /
(cpu_core@FP_ARITH_INST_RETIRED.128B_PACKED_DOUBLE@ +
cpu_core@FP_ARITH_INST_RETIRED.128B_PACKED_SINGLE@)
Testing tma_info_inst_mix_iparith_avx256
FP issues
Cannot resolve IDs for tma_info_inst_mix_iparith_avx256:
cpu_core@INST_RETIRED.ANY@ /
(cpu_core@FP_ARITH_INST_RETIRED.256B_PACKED_DOUBLE@ +
cpu_core@FP_ARITH_INST_RETIRED.256B_PACKED_SINGLE@)
Testing tma_info_inst_mix_iparith_scalar_dp
FP issues
Cannot resolve IDs for tma_info_inst_mix_iparith_scalar_dp:
cpu_core@INST_RETIRED.ANY@ /
cpu_core@FP_ARITH_INST_RETIRED.SCALAR_DOUBLE@
Testing tma_info_inst_mix_iparith_scalar_sp
FP issues
Cannot resolve IDs for tma_info_inst_mix_iparith_scalar_sp:
cpu_core@INST_RETIRED.ANY@ /
cpu_core@FP_ARITH_INST_RETIRED.SCALAR_SINGLE@

Thanks,
Tom
> 
> Thanks,
> Ian


  reply	other threads:[~2025-02-05  4:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 21:32 [PATCH v4 00/23] Intel vendor events and TMA 5.01 metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 01/23] perf vendor events: Update Alderlake events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 02/23] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 03/23] perf vendor events: Add Arrowlake events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 04/23] perf vendor events: Update Broadwell events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 05/23] perf vendor events: Update BroadwellDE events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 06/23] perf vendor events: Update BroadwellX events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 07/23] perf vendor events: Update CascadelakeX events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 08/23] perf vendor events: Add Clearwaterforest events Ian Rogers
2025-02-04 21:32 ` [PATCH v4 09/23] perf vendor events: Update EmeraldRapids events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 10/23] perf vendor events: Update GrandRidge events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 11/23] perf vendor events: Update/add Graniterapids events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 12/23] perf vendor events: Update Haswell events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 13/23] perf vendor events: Update HaswellX events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 14/23] perf vendor events: Update Icelake events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 15/23] perf vendor events: Update IcelakeX events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 16/23] perf vendor events: Update/add Lunarlake events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 17/23] perf vendor events: Update Meteorlake events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 18/23] perf vendor events: Update Rocketlake events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 19/23] perf vendor events: Update Sapphirerapids events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 20/23] perf vendor events: Update Sierraforest events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 21/23] perf vendor events: Update Skylake metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 22/23] perf vendor events: Update SkylakeX events/metrics Ian Rogers
2025-02-04 21:32 ` [PATCH v4 23/23] perf vendor events: Update Tigerlake events/metrics Ian Rogers
2025-02-04 21:35 ` [PATCH v4 00/23] Intel vendor events and TMA 5.01 metrics Ian Rogers
2025-02-05  4:28   ` Falcon, Thomas [this message]
2025-02-05  4:58     ` Ian Rogers
2025-02-05 15:46       ` Liang, Kan
2025-02-05 16:35         ` 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=d44036481022c27d83ce0faf8c7f77042baedb34.camel@intel.com \
    --to=thomas.falcon@intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=afaerber@suse.de \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=caleb.biggers@intel.com \
    --cc=edward.baker@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=manivannan.sadhasivam@linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=perry.taylor@intel.com \
    --cc=peterz@infradead.org \
    --cc=samantha.alt@intel.com \
    --cc=weilin.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox