From: Mark Rutland <mark.rutland@arm.com>
To: Leo Yan <leo.yan@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Oliver Upton <oupton@kernel.org>,
Shameer Kolothum <skolothumtho@nvidia.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: REQUEST: Syncing tools/arch/arm64/include/asm/cputype.h with the kernel sources
Date: Mon, 16 Mar 2026 09:51:10 +0000 [thread overview]
Message-ID: <abfSjoaZYrSqmIdA@J2N7QTR9R3> (raw)
In-Reply-To: <20260316094344.GA8048@e132581.arm.com>
On Mon, Mar 16, 2026 at 09:43:44AM +0000, Leo Yan wrote:
> Hi Arnaldo,
>
> [ + Mark ]
>
> On Sun, Mar 15, 2026 at 10:43:03AM -0300, Arnaldo Carvalho de Melo wrote:
> > Hi,
> >
> > Can someone please address this perf build warning:
> >
> > make: Entering directory '/home/acme/git/perf-tools/tools/perf'
> > BUILD: Doing 'make -j32' parallel build
> > Warning: Kernel ABI header differences:
> > diff -u tools/arch/arm64/include/asm/cputype.h arch/arm64/include/asm/cputype.h
> >
> > I tried updating that header and got the problems below.
> >
> > I just merged perf-tools with upstream, will push to tmp.perf-tools at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tmp.perf-tools
> >
> > Thanks in advance,
>
> Sorry that this issue has come up again.
>
> A quick summary:
>
> The plan was to extract the CPU ID definitions from cputype.h so that
> kernel and userspace can share the same definitions. This would avoid
> keep syncing cputype.h between the kernel and userspace [1].
>
> James worked on this a bit, and later Mark wanted to try a different
> implementation. However, we haven't posted formal patches yet.
>
> To avoid extra burden on perf maintainers, I suggest removing the
> cputype.h check in check-headers.sh. In the short term, Arm developers
> will take responsibility for keeping it up to date. In the long term,
> once the CPU ID refactoring is completed, we can do a proper cleanup of
> cputype.h.
>
> James, Mark, is this reasonable?
>
> [1] https://lore.kernel.org/linux-perf-users/aFJ8bQh_30JMzF_-@J2N7QTR9R3/
Removing the check sounds good to me; that's one of the options I
suggested in [1]:
| The simple solution for now is to *NOT* update the userspace header,
| and to stop warning that this has diverged from the kernel header.
I think it's fine if we need to manually update that header when
teaching the perf tool about specific CPUs.
Are you happy to spin a patch to remove the check?
Mark.
next prev parent reply other threads:[~2026-03-16 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 13:43 REQUEST: Syncing tools/arch/arm64/include/asm/cputype.h with the kernel sources Arnaldo Carvalho de Melo
2026-03-16 9:43 ` Leo Yan
2026-03-16 9:51 ` Mark Rutland [this message]
2026-03-16 10:18 ` Leo Yan
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=abfSjoaZYrSqmIdA@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=oupton@kernel.org \
--cc=skolothumtho@nvidia.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