From: Conor Dooley <conor.dooley@microchip.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: <palmer@dabbelt.com>, <conor@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Heiko Stuebner <heiko.stuebner@vrull.eu>,
Anup Patel <apatel@ventanamicro.com>,
Jisheng Zhang <jszhang@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] RISC-V: Fixes for riscv_has_extension[un]likely()'s alternative dependency
Date: Fri, 24 Mar 2023 11:37:05 +0000 [thread overview]
Message-ID: <e7a93223-54e4-4c97-b121-5d1be3af0d65@spud> (raw)
In-Reply-To: <20230324113107.djp4ejnlpzn3qzrb@orel>
[-- Attachment #1: Type: text/plain, Size: 3058 bytes --]
On Fri, Mar 24, 2023 at 12:31:07PM +0100, Andrew Jones wrote:
> On Fri, Mar 24, 2023 at 10:05:37AM +0000, Conor Dooley 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
> >
> > To prevent "depends on !XIP_KERNEL; select RISCV_ALTERNATIVE" spreading
> > like the plague through the various places that want to check for the
> > presence of extensions, and sidestep the potential silent "success"
> > mentioned above, all users RISCV_ALTERNATIVE are converted from selects
> > to dependencies, with the option being selected for all !XIP_KERNEL
> > builds.
> >
> > I know that the VDSO was a key place that Jisheng wanted to use the new
> > helper rather than static branches, and I think the fallback path
> > should not cause issues there.
> >
> > See the thread at [1] for the prior discussion.
> >
> > Cheers,
> > Conor.
> >
> > 1 - https://lore.kernel.org/linux-riscv/20230128172856.3814-1-jszhang@kernel.org/T/#m21390d570997145d31dd8bb95002fd61f99c6573
> >
> > CC: Paul Walmsley <paul.walmsley@sifive.com>
> > CC: Palmer Dabbelt <palmer@dabbelt.com>
> > CC: Conor Dooley <conor.dooley@microchip.com>
> > CC: Heiko Stuebner <heiko.stuebner@vrull.eu>
> > CC: Andrew Jones <ajones@ventanamicro.com>
> > CC: Anup Patel <apatel@ventanamicro.com>
> > CC: Jisheng Zhang <jszhang@kernel.org>
> > CC: Andrew Jones <ajones@ventanamicro.com>
> > CC: Jason A. Donenfeld <Jason@zx2c4.com>
> > CC: linux-riscv@lists.infradead.org
> > CC: linux-kernel@vger.kernel.org
> >
> > Conor Dooley (2):
> > RISC-V: add non-alternative fallback for
> > riscv_has_extension_[un]likely()
> > RISC-V: always select RISCV_ALTERNATIVE for non-xip kernels
> >
> > arch/riscv/Kconfig | 12 ++++----
> > arch/riscv/Kconfig.erratas | 6 ++--
> > arch/riscv/include/asm/hwcap.h | 50 ++++++++++++++++++++--------------
> > 3 files changed, 38 insertions(+), 30 deletions(-)
> >
> > --
> > 2.39.2
> >
>
> LGTM, but if it was based on for-next then it could also immediately be
> applied to zicboz. For the series,
Hmm, I did it on top of fixes since this needs to go into v6.3.
Perhaps I can create a standalone patch for Zicboz and Palmer could merge
these two into both fixes & for-next, with the standalone applied on
top?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-24 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:05 Conor Dooley
2023-03-24 10:05 ` [PATCH v1 1/2] RISC-V: add non-alternative fallback for riscv_has_extension_[un]likely() Conor Dooley
2023-03-24 10:05 ` [PATCH v1 2/2] RISC-V: always select RISCV_ALTERNATIVE for non-xip kernels Conor Dooley
2023-03-24 11:31 ` [PATCH v1 0/2] RISC-V: Fixes for riscv_has_extension[un]likely()'s alternative dependency Andrew Jones
2023-03-24 11:37 ` Conor Dooley [this message]
2023-03-24 11:43 ` Andrew Jones
2023-03-24 13:20 ` Jason A. Donenfeld
2023-03-30 21:02 ` Palmer Dabbelt
2023-03-30 21:10 ` patchwork-bot+linux-riscv
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=e7a93223-54e4-4c97-b121-5d1be3af0d65@spud \
--to=conor.dooley@microchip.com \
--cc=Jason@zx2c4.com \
--cc=ajones@ventanamicro.com \
--cc=apatel@ventanamicro.com \
--cc=conor@kernel.org \
--cc=heiko.stuebner@vrull.eu \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®