From: Ali Saidi <alisaidi@amazon.com>
To: <leo.yan@linaro.org>
Cc: <acme@kernel.org>, <catalin.marinas@arm.com>, <will@kernel.org>,
<john.g.garry@oracle.com>, <james.clark@arm.com>,
<mike.leach@linaro.org>, <peterz@infradead.org>,
<mingo@redhat.com>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<namhyung@kernel.org>, <irogers@google.com>,
<adrian.hunter@intel.com>, <scott@os.amperecomputing.com>,
<maz@kernel.org>, <anshuman.khandual@arm.com>,
<german.gomez@arm.com>, <alisaidi@amazon.com>,
<renyu.zj@linux.alibaba.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <fissure2010@gmail.com>
Subject: Re: [PATCH v1 0/3] arm64: Support Cortex-X4 CPU for Perf Arm SPE
Date: Fri, 21 Jul 2023 18:16:53 +0000 [thread overview]
Message-ID: <20230721181653.22398-1-alisaidi@amazon.com> (raw)
In-Reply-To: <20230717054327.79815-1-leo.yan@linaro.org>
Hi Leo,
On Mon, 17 Jul 2023 05:43:24 +0000, Leo Yan wrote:
> This series support Cortex-X4 CPU in Perf Arm SPE.
>
> The Arm64 and tools both include the header cputype.h for CPU part and
> MIDR definitions, to de-couple between the tools and the kernel, the
> tools doesn't directly use the kernel's header, alternatively, the tools
> maintain a copy and sync with kernel's header.
>
> To keep the exact same content between kernel and tools' headers, this
> series firstly adds Cortex-X4 CPU part and MIDR definitions in the
> kernel header; then the second patch syncs the change into the tools'
> header. The first patch is to support the Cortex-X4 in perf Arm SPE
> with the new CPU definitions.
>
> I don't have Cortex-X4 machine in hand, so just verified with
> compilation perf tool.
This looks good to me, but can we add the other cores that operate the
same way now too? Flipping through the TRMs A78, X3, V2, X1, A715,
A720, and A78C all have the same encodings.
Reviewed-by: Ali Saidi <alisaidi@amazon.com>
Thanks!
Ali
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-21 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 5:43 [PATCH v1 0/3] arm64: Support Cortex-X4 CPU for Perf Arm SPE Leo Yan
2023-07-17 5:43 ` [PATCH v1 1/3] arm64: Add Cortex-X4 CPU part definitions Leo Yan
2023-07-17 5:43 ` [PATCH v1 2/3] tools headers arm64: Sync " Leo Yan
2023-07-17 5:43 ` [PATCH v1 3/3] perf arm-spe: Support data source for Cortex-X4 CPU Leo Yan
[not found] ` <c784911e-72f4-8150-530b-234978546a45@arm.com>
[not found] ` <20230724110509.GA76473@leoy-huanghe.lan>
2023-07-28 14:22 ` Will Deacon
2023-07-21 18:16 ` Ali Saidi [this message]
[not found] ` <20230724113013.GB76473@leoy-huanghe.lan>
2023-07-28 14:38 ` [PATCH v1 0/3] arm64: Support Cortex-X4 CPU for Perf Arm SPE Arnaldo Carvalho de Melo
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=20230721181653.22398-1-alisaidi@amazon.com \
--to=alisaidi@amazon.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fissure2010@gmail.com \
--cc=german.gomez@arm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=scott@os.amperecomputing.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).