From: James Clark <james.clark@arm.com>
To: "Suzuki K Poulose" <suzuki.poulose@arm.com>,
	"Leo Yan" <leo.yan@linaro.org>, 蔡沅信 <fissure2010@gmail.com>,
	"Mark Rutland" <mark.rutland@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Some questions about using the perf tool in ARM-SPE
Date: Mon, 3 Jul 2023 09:24:27 +0100	[thread overview]
Message-ID: <f811f7ce-bf04-b5af-ee33-ea489927649f@arm.com> (raw)
In-Reply-To: <cf180f9a-085b-ad9b-c477-f02d32559c0a@arm.com>
On 03/07/2023 09:18, Suzuki K Poulose wrote:
> Hi Leo
> On 14/06/2023 02:21, Leo Yan wrote:
>> Hi,
>>
>> On Tue, Jun 13, 2023 at 09:23:33PM +0800, 蔡沅信 wrote:
>>> OK
>>> I have a new discovery that c2c seems to support only certain Arm
>>> Neoverse (N1/N2/V1) CPUs, I wonder if cortex-X4 could support it?
>>
>> Based on Cortex-X4 TRM [1], we can see Cortex-X4 has the same SPE data
>> source packet format with Neoverse CPUs.  In theory, we can add
>> Cortex-X4's MIDR into the neoverse_spe[] array in
>> tools/perf/util/arm-spe.c to support Cortex-X4.
>>
>> Linux master branch misses the definition for Cortex-X4's MIDR [2],
>> Mark.R / Suzuki / James, could you confirm if Arm has plan or already
>> has patches for enabling Cortex-X4's MIDR?
>>
> 
> Is there a particular reason why need this in the kernel ? Usual
> policy is, kernel needs to distinguish an MIDR, only if it ever
> needs to. e.g, a CPU erratum specific to the MIDR.
> 
> Suzuki>
This is on the tool side rather than in the kernel. But yes, if the data
source encoding is the same as the existing ones please send a patch
adding X4's MIDR to the list.
Thanks
James
next prev parent reply	other threads:[~2023-07-03  8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  7:14 Some questions about using the perf tool in ARM-SPE 蔡沅信
2023-06-09  9:06 ` James Clark
     [not found]   ` <CALDTKqg01+xJ2xu218c_QH2PbX9wdhYOiJfDieCXL5PHWV-6FQ@mail.gmail.com>
     [not found]     ` <77773641-26e5-a754-63cf-e7d3443e11fc@arm.com>
2023-06-13 13:23       ` 蔡沅信
2023-06-14  1:21         ` Leo Yan
     [not found]           ` <CALDTKqgz6=WFs=bMvnFkKv5kt5OP5wtUqQ2uekVbumCxNqeRXw@mail.gmail.com>
2023-06-14  6:08             ` 蔡沅信
2023-06-18  9:28               ` Leo Yan
2023-07-01  5:25                 ` 蔡沅信
2023-07-03  8:18           ` Suzuki K Poulose
2023-07-03  8:24             ` James Clark [this message]
2023-07-03  9:39               ` Leo Yan
2023-07-03  9:42                 ` James Clark
2023-07-03 10:20                   ` Leo Yan
2023-07-03 13:28                     ` Suzuki K Poulose
2023-07-05 17:33                       ` Namhyung Kim
2023-07-17  5:57                         ` Leo Yan
2023-07-17  9:05                           ` Suzuki K Poulose
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=f811f7ce-bf04-b5af-ee33-ea489927649f@arm.com \
    --to=james.clark@arm.com \
    --cc=fissure2010@gmail.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).