From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Will Deacon" <will@kernel.org>,
"David Laight" <david.laight.linux@gmail.com>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
"Jisheng Zhang" <jszhang@kernel.org>
Subject: Re: [PATCH v3 2/7] arm64/runtime-const: Use aarch64_insn_patch_text_nosync() for patching
Date: Sun, 12 Apr 2026 01:24:45 +0530 [thread overview]
Message-ID: <c45ede13-f8d0-4b6a-b2ed-f06af4882ebc@amd.com> (raw)
In-Reply-To: <adjE6WzFM7NogzlU@arm.com>
Hello Catalin,
Thank you for taking a look at the series and pointing to the Shashiko
review.
On 4/10/2026 3:07 PM, Catalin Marinas wrote:
>> -static inline void __runtime_fixup_caches(void *where, unsigned int insns)
>> -{
>> - unsigned long va = (unsigned long)where;
>> - caches_clean_inval_pou(va, va + 4*insns);
>> + aarch64_insn_patch_text_nosync(p, insn);
>> }
>
> Sashiko has some good points here:
Ack! I did check the Sashiko review a few days after posting. I think
I'll probably start replying to Shahsiko's inline review on future
threads on LKML to keep the record like some folks are doing.
>
> https://sashiko.dev/#/patchset/20260402112250.2138-1-kprateek.nayak@amd.com
>
> In short, aarch64_insn_patch_text_nosync() does not expect a linear map
> address but rather a kernel text one (or vmalloc/modules). The other
> valid point is on aliasing I-caches.
>
> I think dropping the lm_alias() and just use 'where' directly would do
> but I haven't tried.
Ack! I completely missed that subtlety of passing "where" to
caches_clean_inval_pou(). I'm still surprised that it didn't
blow up in my testing.
Anyhow, following diff, on top of the full series builds and
tests fine and has been blessed by review-prompts:
diff --git a/arch/arm64/include/asm/runtime-const.h b/arch/arm64/include/asm/runtime-const.h
index 21f817eb5951..d3f0dfa7ced0 100644
--- a/arch/arm64/include/asm/runtime-const.h
+++ b/arch/arm64/include/asm/runtime-const.h
@@ -57,21 +57,21 @@
} while (0)
/* 16-bit immediate for wide move (movz and movk) in bits 5..20 */
-static inline void __runtime_fixup_16(__le32 *p, unsigned int val)
+static inline void __runtime_fixup_16(void *where, unsigned int val)
{
+ __le32 *p = lm_alias(where);
u32 insn = le32_to_cpu(*p);
insn &= 0xffe0001f;
insn |= (val & 0xffff) << 5;
- aarch64_insn_patch_text_nosync(p, insn);
+ aarch64_insn_patch_text_nosync(where, insn);
}
static inline void __runtime_fixup_ptr(void *where, unsigned long val)
{
- __le32 *p = lm_alias(where);
- __runtime_fixup_16(p, val);
- __runtime_fixup_16(p+1, val >> 16);
- __runtime_fixup_16(p+2, val >> 32);
- __runtime_fixup_16(p+3, val >> 48);
+ __runtime_fixup_16(where, val);
+ __runtime_fixup_16(where + 4, val >> 16);
+ __runtime_fixup_16(where + 8, val >> 32);
+ __runtime_fixup_16(where + 12, val >> 48);
}
/* Immediate value is 6 bits starting at bit #16 */
@@ -81,15 +81,14 @@ static inline void __runtime_fixup_shift(void *where, unsigned long val)
u32 insn = le32_to_cpu(*p);
insn &= 0xffc0ffff;
insn |= (val & 63) << 16;
- aarch64_insn_patch_text_nosync(p, insn);
+ aarch64_insn_patch_text_nosync(where, insn);
}
/* Immediate value is 6 bits starting at bit #16 */
static inline void __runtime_fixup_mask(void *where, unsigned long val)
{
- __le32 *p = lm_alias(where);
- __runtime_fixup_16(p, val);
- __runtime_fixup_16(p+1, val >> 16);
+ __runtime_fixup_16(where, val);
+ __runtime_fixup_16(where + 4, val >> 16);
}
static inline void runtime_const_fixup(void (*fn)(void *, unsigned long),
---
I'll do some more sanity checks and address the rest of the comments
before posting out v4 soon after the merge window. Thank you again
for your feedback. Much appreciated.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-04-11 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 11:22 [PATCH v3 0/7] futex: Use runtime constants for futex_hash computation K Prateek Nayak
2026-04-02 11:22 ` [PATCH v3 1/7] x86/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-04-02 11:22 ` [PATCH v3 2/7] arm64/runtime-const: Use aarch64_insn_patch_text_nosync() for patching K Prateek Nayak
2026-04-10 9:37 ` Catalin Marinas
2026-04-11 19:54 ` K Prateek Nayak [this message]
2026-04-02 11:22 ` [PATCH v3 3/7] arm64/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-04-02 11:22 ` [PATCH v3 4/7] riscv/runtime-const: " K Prateek Nayak
2026-04-03 9:42 ` Guo Ren
2026-04-03 10:35 ` K Prateek Nayak
2026-04-02 11:22 ` [PATCH v3 5/7] s390/runtime-const: " K Prateek Nayak
2026-04-02 11:22 ` [PATCH v3 6/7] asm-generic/runtime-const: Add dummy runtime_const_mask_32() K Prateek Nayak
2026-04-02 11:22 ` [PATCH v3 7/7] futex: Use runtime constants for __futex_hash() hot path K Prateek Nayak
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=c45ede13-f8d0-4b6a-b2ed-f06af4882ebc@amd.com \
--to=kprateek.nayak@amd.com \
--cc=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=dave@stgolabs.net \
--cc=david.laight.linux@gmail.com \
--cc=dvhart@infradead.org \
--cc=jszhang@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=will@kernel.org \
/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