From: Mark Rutland <mark.rutland@arm.com>
To: James Clark <james.clark@linaro.org>
Cc: Yicong Yang <yangyicong@huawei.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Ali Saidi <alisaidi@amazon.com>, Leo Yan <leo.yan@linaro.org>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Jinqian Yang <yangjinqian1@huawei.com>,
Douglas Anderson <dianders@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Yicong Yang <yangyicong@hisilicon.com>
Subject: Re: perf usage of arch/arm64/include/asm/cputype.h
Date: Mon, 16 Jun 2025 18:41:20 +0100 [thread overview]
Message-ID: <aFBXQGeYCO2nJYNG@J2N7QTR9R3> (raw)
In-Reply-To: <2abcf4ec-4725-4e79-b8d3-a4ddbc00caba@linaro.org>
On Mon, Jun 16, 2025 at 10:29:48AM +0100, James Clark wrote:
> I was also wondering if we could just diverge on the tools side, but in
> reality it also has to stay compatible with the definitions of all the MIDRs
> so might as well keep the whole thing identical.
I think that'd be the best option overall.
The only thing we really care about updating periodically is the set of
MIDRs, and we can factor that out to a cputype-defs.h header, and
possibly generate that too (as with sysreg-defs.h).
Mark.
prev parent reply other threads:[~2025-06-16 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aEyGg98z-MkcClXY@x1>
2025-06-16 7:56 ` perf usage of arch/arm64/include/asm/cputype.h Yicong Yang
2025-06-16 9:29 ` James Clark
2025-06-16 9:54 ` Shameerali Kolothum Thodi
2025-06-16 13:07 ` Leo Yan
2025-06-16 15:04 ` Yicong Yang
2025-06-16 16:08 ` Leo Yan
2025-06-16 17:47 ` Mark Rutland
2025-06-17 14:18 ` Leo Yan
2025-06-18 6:47 ` Yicong Yang
2025-06-18 8:52 ` Mark Rutland
2025-06-18 11:24 ` Leo Yan
2025-06-18 11:51 ` Yicong Yang
2025-06-18 13:02 ` Leo Yan
2025-06-18 13:15 ` Arnaldo Carvalho de Melo
2025-06-18 14:44 ` Leo Yan
2025-06-16 17:41 ` Mark Rutland [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=aFBXQGeYCO2nJYNG@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alisaidi@amazon.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=james.morse@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=yangjinqian1@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.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