From: sashiko-bot@kernel.org
To: "K Prateek Nayak" <kprateek.nayak@amd.com>
Cc: "Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-s390@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>
Subject: Re: [PATCH v6 1/8] x86/runtime-const: Introduce runtime_const_mask_32()
Date: Tue, 28 Jul 2026 05:37:22 +0000 [thread overview]
Message-ID: <20260728053722.832811F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728052540.4728-2-kprateek.nayak@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit introduces `runtime_const_mask_32` for x86 but omits a generic fallback in `include/asm-generic/runtime-const.h`.
--
--- Patch [1]: [PATCH v6 1/8] x86/runtime-const: Introduce runtime_const_mask_32() ---
commit 664c491c817106934caf3b46117ff57570227576
Author: Peter Zijlstra <peterz@infradead.org>
x86/runtime-const: Introduce runtime_const_mask_32()
This commit introduces the runtime_const_mask_32() macro for the x86
architecture to optimize the mask operation in the futex hash computation
hot path. It also adds the __runtime_fixup_mask() helper to support
this functionality.
Link: https://patch.msgid.link/20260227161841.GH606826@noisy.programming.kicks-ass.net
> diff --git a/arch/x86/include/asm/runtime-const.h b/arch/x86/include/asm/runtime-const.h
> index 4cd94fdcb45e2..b13f7036c1c9b 100644
> --- a/arch/x86/include/asm/runtime-const.h
> +++ b/arch/x86/include/asm/runtime-const.h
[ ... ]
> @@ -41,6 +41,15 @@
> :"+r" (__ret)); \
> __ret; })
>
> +#define runtime_const_mask_32(val, sym) ({ \
> + typeof(0u+(val)) __ret = (val); \
> + asm_inline("and $0x12345678, %k0\n1:\n" \
> + ".pushsection runtime_mask_" #sym ",\"a\"\n\t"\
> + ".long 1b - 4 - .\n" \
> + ".popsection" \
> + : "+r" (__ret)); \
> + __ret; })
> +
[Severity: Medium]
Will this cause a build regression on non-x86 architectures when the generic
code starts using runtime_const_mask_32()?
The commit message mentions this will be used by the futex hash computation in
a subsequent commit. However, there doesn't appear to be a generic fallback
for this macro in include/asm-generic/runtime-const.h.
Without a generic fallback, it seems architectures that don't support or
haven't yet implemented runtime constants would fail to compile once the
generic futex code uses this macro.
Should a fallback like the following be introduced in
include/asm-generic/runtime-const.h alongside this x86 implementation to
maintain cross-architecture compatibility and strict bisectability?
#define runtime_const_mask_32(val, sym) ((val) & (sym))
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728052540.4728-1-kprateek.nayak@amd.com?part=1
next prev parent reply other threads:[~2026-07-28 5:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 5:25 [PATCH v6 0/8] futex: Use runtime constants for futex_hash computation K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 1/8] x86/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-07-28 5:37 ` sashiko-bot [this message]
2026-07-28 8:21 ` K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 2/8] arm64/runtime-const: Use aarch64_insn_patch_text_nosync() for patching K Prateek Nayak
2026-07-28 5:35 ` sashiko-bot
2026-07-28 5:25 ` [PATCH v6 3/8] arm64/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-07-28 5:36 ` sashiko-bot
2026-07-28 5:25 ` [PATCH v6 4/8] riscv/runtime-const: Replace open-coded placeholder with RUNTIME_MAGIC K Prateek Nayak
2026-07-28 5:34 ` sashiko-bot
2026-07-28 5:25 ` [PATCH v6 5/8] riscv/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-07-28 5:38 ` sashiko-bot
2026-07-28 5:25 ` [PATCH v6 6/8] s390/runtime-const: " K Prateek Nayak
2026-07-28 5:36 ` sashiko-bot
2026-07-28 5:25 ` [PATCH v6 7/8] asm-generic/runtime-const: Add dummy runtime_const_mask_32() K Prateek Nayak
2026-07-28 5:34 ` sashiko-bot
2026-07-28 5:25 ` [PATCH v6 8/8] futex: Use runtime constants for __futex_hash() hot path K Prateek Nayak
2026-07-28 5:42 ` sashiko-bot
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=20260728053722.832811F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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