Linux Perf Users
 help / color / mirror / Atom feed
From: TAKANO Mitsuhiro <takano32@gmail.com>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ilkka Koskinen <ilkka@os.amperecomputing.com>,
	linux-perf-users@vger.kernel.org,
	Namhyung Kim <namhyung@kernel.org>,
	TAKANO Mitsuhiro <takano32@gmail.com>
Subject: Re: [PATCH] perf vendor events arm64 AmpereOneX: Drop stale BPU_FLUSH_MEM_FAULT entry
Date: Fri, 30 Oct 2026 05:37:44 +0000	[thread overview]
Message-ID: <179333866449.669133.15101451727175644059@gmail.com> (raw)
In-Reply-To: <CAP-5=fX+2eRGCHcU43sqU=gi9iKvxqyS6ipwRSnvFcap3D+QzQ@mail.gmail.com>

Hi Ian,

Agreed, and v2 is in this thread: the entry stays and is marked
deprecated, with the description worded the way the x86 tables word it,
so perf list shows the counter once and a script that names
BPU_FLUSH_MEM_FAULT keeps working.

Ilkka, your Acked-by is on v2 as well, since you said either option was
fine -- say so and I will drop it rather than have it look like you
acked a diff you did not read.

On Arnaldo's jevents.py question: a general duplicate-EventCode check is
not possible for the reasons you gave.  Across the 1463 raw EventCode
entries under arch/arm64 this is the only duplicated code, so a check
limited to those tables would flag this and nothing else in the tree
today.  I can send that separately if it is thought worth having.

Thanks,
Mitsuhiro


      parent reply	other threads:[~2026-10-30  5:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 22:45 [PATCH] perf vendor events arm64 AmpereOneX: Drop stale BPU_FLUSH_MEM_FAULT entry TAKANO Mitsuhiro
2026-10-21 22:48 ` sashiko-bot
2026-10-27 20:34 ` Arnaldo Carvalho de Melo
2026-10-27 21:37   ` Ian Rogers
2026-10-29  1:09     ` Ilkka Koskinen
2026-10-30  5:37     ` TAKANO Mitsuhiro [this message]

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=179333866449.669133.15101451727175644059@gmail.com \
    --to=takano32@gmail.com \
    --cc=acme@kernel.org \
    --cc=ilkka@os.amperecomputing.com \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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