[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgq4kMyeyhSm-Hrw1cQMi81=2JGznyVugeCejJoy1QSwg@mail.gmail.com>
Date: Tue, 11 Jun 2024 11:59:21 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Mark Rutland <mark.rutland@....com>
Cc: Peter Anvin <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
Thomas Gleixner <tglx@...utronix.de>, Rasmus Villemoes <linux@...musvillemoes.dk>,
Josh Poimboeuf <jpoimboe@...nel.org>, Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>, linux-arm-kernel@...ts.infradead.org,
linux-arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH 4/7] arm64: add 'runtime constant' support
On Tue, 11 Jun 2024 at 10:59, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> So I'll look at doing this for x86 and see how it works.
Oh - and when I started looking at it, I immediately remembered why I
didn't want to use alternatives originally.
The alternatives are finalized much too early for this. By the time
the dcache code works, the alternatives have already been applied.
I guess all the arm64 alternative callbacks are basically finalized
very early, basically when the CPU models etc have been setup.
We could do a "late alternatives", I guess, but now it's even more
infrastructure just for the constants.
Linus
Powered by blists - more mailing lists