From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Leo Yan <leo.yan@linaro.org>, Namhyung Kim <namhyung@gmail.com>
Cc: "James Clark" <james.clark@arm.com>, 蔡沅信 <fissure2010@gmail.com>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-perf-users@vger.kernel.org,
"Arnaldo Carvalho de Melo" <acme@kernel.org>
Subject: Re: Some questions about using the perf tool in ARM-SPE
Date: Mon, 17 Jul 2023 10:05:08 +0100 [thread overview]
Message-ID: <14ebfd67-02e1-72a5-38fa-119a2886a268@arm.com> (raw)
In-Reply-To: <20230717055713.GA79840@leoy-huanghe.lan>
On 17/07/2023 06:57, Leo Yan wrote:
> Hi Suzuki,
>
> On Wed, Jul 05, 2023 at 10:33:18AM -0700, Namhyung Kim wrote:
>> On Mon, Jul 3, 2023 at 6:33 AM Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
>>> On 03/07/2023 11:20, Leo Yan wrote:
>>>> On Mon, Jul 03, 2023 at 10:42:21AM +0100, James Clark wrote:
>
> [...]
>
>>> Do we somehow sync (copy) the cputype.h for perf tool ? Or do we keep
>>> them in sync with a patch ?
>>>
>>> If it is the former, I wouldn't bother about updating the kernel
>>> headers.
>>
>> In general, perf tool has a copy of kernel headers and there's a script
>> called check-headers.sh to verify they are in sync. We don't
>> recommend kernel patches to touch the tool's copy. And it's done
>> by tool devs separately.
>
> We have the kernel header arch/arm64/include/asm/cputype.h, tools have a
> copy which is placed in tools/arch/arm64/include/asm/cputype.h.
>
> As Namhyung explained, usually the kernel header is firstly changed and
> then the tool developers send a separate patch to sync with kernel
> header. You could see a recent example by Arnaldo's patch [1].
>
> By following this working model, I sent patch series to add Cortex-X4
> CPU part and MIDR definitions. I personally think this is the best
> way for us to keep the alignment between the kernel header and tools
> header [2]. Please let me know if this doable or not?
Sure, if the tool relies on syncing the kernel headers, thats fine.
>
> Sorry for late response due to vacation :)
No worries, I will dig the series from the mailing list and
respond there. Thanks for sending this out.
Suzuki
>
> Thanks,
> Leo
>
> [1] https://lore.kernel.org/lkml/ZLFQ%2Ftu%2FATQwDEIW@kernel.org/
> [2] https://lore.kernel.org/lkml/20230717054327.79815-1-leo.yan@linaro.org/
prev parent reply other threads:[~2023-07-17 9:05 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
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 [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=14ebfd67-02e1-72a5-38fa-119a2886a268@arm.com \
--to=suzuki.poulose@arm.com \
--cc=acme@kernel.org \
--cc=fissure2010@gmail.com \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@gmail.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).