[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD=FV=UrG+1vVPRGp+CM9Ws64DJd01G6qq+JunF06kaiMJ=zXg@mail.gmail.com>
Date: Fri, 13 Jun 2025 13:53:20 -0700
From: Doug Anderson <dianders@...omium.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Yicong Yang <yangyicong@...ilicon.com>, Ali Saidi <alisaidi@...zon.com>,
Leo Yan <leo.yan@...aro.org>, Will Deacon <will@...nel.org>, James Morse <james.morse@....com>,
Catalin Marinas <catalin.marinas@....com>, Jinqian Yang <yangjinqian1@...wei.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>, Adrian Hunter <adrian.hunter@...el.com>,
Ian Rogers <irogers@...gle.com>, James Clark <james.clark@...aro.org>,
Jiri Olsa <jolsa@...nel.org>, Kan Liang <kan.liang@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Oliver Upton <oliver.upton@...ux.dev>,
Shameer Kolothum <shameerali.kolothum.thodi@...wei.com>, Sebastian Ott <sebott@...hat.com>,
Cornelia Huck <cohuck@...hat.com>
Subject: Re: perf usage of arch/arm64/include/asm/cputype.h
Hi,
On Fri, Jun 13, 2025 at 1:14 PM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> Hi,
>
> tools/perf (and other tools/ living code) uses a file from the kernel, a
> copy, so that we don't break its build when something changes in the
> kernel that tooling uses.
>
> There is this tools/perf/check-headers.sh that does the "copy coherency
> check", while trying to act on such a warning I stumbled on the report
> below.
>
> More details at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/include/uapi/README
>
>
> If you could please take a look at this that would be great, the initial
> copy was made at:
I'm not sure exactly what you're asking folks to do, but my guess is
that you got broken by:
e3121298c7fc ("arm64: Modify _midr_range() functions to read
MIDR/REVIDR internally")
Powered by blists - more mailing lists