[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168021061833.10339.16976818508528489046.git-patchwork-notify@kernel.org>
Date: Thu, 30 Mar 2023 21:10:18 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Conor Dooley <conor.dooley@...rochip.com>
Cc: linux-riscv@...ts.infradead.org, palmer@...belt.com,
conor@...nel.org, paul.walmsley@...ive.com,
heiko.stuebner@...ll.eu, ajones@...tanamicro.com,
apatel@...tanamicro.com, jszhang@...nel.org, Jason@...c4.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/2] RISC-V: Fixes for riscv_has_extension[un]likely()'s
alternative dependency
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@...osinc.com>:
On Fri, 24 Mar 2023 10:05:37 +0000 you wrote:
> Here's my attempt at fixing both the use of an FPU on XIP kernels and
> the issue that Jason ran into where CONFIG_FPU, which needs the
> alternatives frame work for has_fpu() checks, could be enabled without
> the alternatives actually being present.
>
> For the former, a "slow" fallback that does not use alternatives is
> added to riscv_has_extension_[un]likely() that can be used with XIP.
> Obviously, we want to make use of Jisheng's alternatives based approach
> where possible, so any users of riscv_has_extension_[un]likely() will
> want to make sure that they select RISCV_ALTERNATIVE.
> If they don't however, they'll hit the fallback path which (should,
> sparing a silly mistake from me!) behave in the same way, thus
> succeeding silently. Sounds like a
>
> [...]
Here is the summary with links:
- [v1,1/2] RISC-V: add non-alternative fallback for riscv_has_extension_[un]likely()
https://git.kernel.org/riscv/c/1aa866931b80
- [v1,2/2] RISC-V: always select RISCV_ALTERNATIVE for non-xip kernels
https://git.kernel.org/riscv/c/1ee7fc3f4d0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists