All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chun-Tse Shao" <ctshao@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 1/6] perf vendor events intel: Update arrowlake events from 1.17 to 1.19
Date: Tue, 09 Jun 2026 22:01:14 +0000	[thread overview]
Message-ID: <20260609220115.43C531F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260609215046.2391903-2-ctshao@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `UMask` field was erroneously deleted from the `BR_INST_RETIRED.COND_TAKEN_FWD` event definition, causing it to silently alias to `BR_INST_RETIRED.ALL_BRANCHES`.
--

commit a0347536085c6d8e17e90fb1536ff53c3e33e1ee
Author: Chun-Tse Shao <ctshao@google.com>

perf vendor events intel: Update arrowlake events from 1.17 to 1.19

This commit updates the Intel Arrowlake performance monitoring events from
version 1.17 to 1.19. The updated events were published in the upstream
perfmon repository.

Link: https://github.com/intel/perfmon/commit/b84e75626ae78558b8f526a276e4597c5ca6c429

> diff --git a/tools/perf/pmu-events/arch/x86/arrowlake/pipeline.json b/tools/perf/pmu-events/arch/x86/arrowlake/pipeline.json
> index a0fd63cace220..bdfee0347cc5a 100644
> --- a/tools/perf/pmu-events/arch/x86/arrowlake/pipeline.json
> +++ b/tools/perf/pmu-events/arch/x86/arrowlake/pipeline.json
[ ... ]
> @@ -209,7 +209,6 @@
>          "EventName": "BR_INST_RETIRED.COND_TAKEN_FWD",
>          "PublicDescription": "Counts taken forward conditional branch instructions retired. Available PDIST counters: 0,1",
>          "SampleAfterValue": "400009",
> -        "UMask": "0x102",

[Severity: Medium]
Was it intentional to completely remove the UMask field from
BR_INST_RETIRED.COND_TAKEN_FWD instead of updating it?

When a PMU event has no UMask specified, the perf event parser defaults the
umask to 0x00. Since BR_INST_RETIRED.ALL_BRANCHES uses EventCode 0xc4
without a UMask, the BR_INST_RETIRED.COND_TAKEN_FWD event (also 0xc4) now
perfectly aliases to ALL_BRANCHES.

This breaks top-down microarchitecture analysis metrics that rely on it,
such as tma_info_bad_spec_ipmisp_cond_taken_fwd, as the metric expression
cpu_core@BR_INST_RETIRED.COND_TAKEN_FWD@ /
cpu_core@BR_INST_RETIRED.ALL_BRANCHES@ will erroneously evaluate to exactly
1.0.

>          "Unit": "cpu_core"
>      },
>      {

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260609215046.2391903-1-ctshao@google.com?part=1

  reply	other threads:[~2026-06-09 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 21:50 [PATCH v1 0/6] perf vendor events intel: update Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 1/6] perf vendor events intel: Update arrowlake events from 1.17 to 1.19 Chun-Tse Shao
2026-06-09 22:01   ` sashiko-bot [this message]
2026-06-09 21:50 ` [PATCH v1 2/6] perf vendor events intel: Update emeraldrapids events from 1.23 to 1.24 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 3/6] perf vendor events intel: Update graniterapids events from 1.18 to 1.19 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 4/6] perf vendor events intel: Update lunarlake events from 1.22 to 1.25 Chun-Tse Shao
2026-06-09 22:02   ` sashiko-bot
2026-06-09 22:58     ` Chun-Tse Shao
2026-06-10  9:04       ` Mi, Dapeng
2026-06-09 21:50 ` [PATCH v1 5/6] perf vendor events intel: Update pantherlake events from 1.05 to 1.06 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 6/6] perf vendor events intel: Update tigerlake events from 1.18 to 1.19 Chun-Tse Shao
2026-06-09 21:56   ` sashiko-bot

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=20260609220115.43C531F00898@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ctshao@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.