From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Ali Saidi <alisaidi@amazon.com>,
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,
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, 28 Jul 2023 11:38:11 -0300 [thread overview]
Message-ID: <ZMPS04R7MpnxKwJ0@kernel.org> (raw)
In-Reply-To: <20230724113013.GB76473@leoy-huanghe.lan>
Em Mon, Jul 24, 2023 at 07:30:13PM +0800, Leo Yan escreveu:
> Hi Ali,
>
> On Fri, Jul 21, 2023 at 06:16:53PM +0000, Ali Saidi wrote:
>
> > > This series support Cortex-X4 CPU in Perf Arm SPE.
>
> [...]
>
> > 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.
>
> Thanks a lot for exploring more CPU variants which share the same data
> source packet format.
>
> The latest Linux kernel have defined the CPU part number and MIDR for
> below CPU variants:
>
> - A78
> - X1
> - A715
> - A78C
>
> I would like to use a patch to support these CPUs in perf tool. Given
> other CPU variants (X3/V2/A720) have not been supported in the kernel,
> and so far no one requests them, I would like leave them out.
>
> Please let me know if this okay for you or not.
>
>
> > Reviewed-by: Ali Saidi <alisaidi@amazon.com>
>
> Thanks for review, I will add your review tags in the new patch set.
Ok, waiting for the new patch set.
- Arnaldo
prev parent reply other threads:[~2023-07-28 14:38 UTC|newest]
Thread overview: 12+ 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-24 6:44 ` Anshuman Khandual
2023-07-24 6:55 ` Anshuman Khandual
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
2023-07-24 6:57 ` Anshuman Khandual
2023-07-24 11:05 ` Leo Yan
2023-07-28 14:22 ` Will Deacon
2023-07-21 18:16 ` [PATCH v1 0/3] arm64: Support Cortex-X4 CPU for Perf Arm SPE Ali Saidi
2023-07-24 11:30 ` Leo Yan
2023-07-28 14:38 ` Arnaldo Carvalho de Melo [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=ZMPS04R7MpnxKwJ0@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alisaidi@amazon.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).