[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250827081252.GD745921@e132581.arm.com>
Date: Wed, 27 Aug 2025 09:12:52 +0100
From: Leo Yan <leo.yan@....com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ian Rogers <irogers@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 05/11] tools headers: Sync arm64 headers with the kernel
source
On Mon, Aug 25, 2025 at 02:58:57PM -0700, Namhyung Kim wrote:
[...]
> But the following two changes cannot be applied since they introduced
> new build errors in util/arm-spe.c. So it still has the warning after
> this change.
>
> c8c2647e69bedf80 arm64: Make _midr_in_range_list() an exported function
> e3121298c7fcaf48 arm64: Modify _midr_range() functions to read MIDR/REVIDR internally
Hi Namhyung,
Thanks for working on this. It is on our todo list for automatic
generating MIDR. Sorry for any troubling during the syncing.
Just a minor comment below.
[...]
> +struct target_impl_cpu {
> + u64 midr;
> + u64 revidr;
> + u64 aidr;
> +};
> +
> +bool cpu_errata_set_target_impl(u64 num, void *impl_cpus);
> +
Currently, no one uses this API. It seems to me that we don't need to
sync this code chunk.
Otherwise, other changes LGTM.
Thanks,
Leo
Powered by blists - more mailing lists