From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A15DA33FE2F for ; Tue, 24 Mar 2026 00:00:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774310400; cv=none; b=t1nul6zTMQdMsDgdn7JCwKeOHqZ8exeoKuQELqtiXg79cx+ynHEJ4uxiN2u2un9v5jxtbXdIhCUF3/aIzfzrabFr4BFItpVC2q7hdPSnad7RnzHRvgaZPvgWf5gU8aRm9GaYmxL8RI22FbZo+X2qywEpuiWXNMNRu4Td4akCEQ0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774310400; c=relaxed/simple; bh=qJyAYAiz0wfqqJjBKxAwZyVPhPLmb0z+stL3H8W7gLA=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=KIfX88txgPkAipRHbKtZRFjlP5Pi/zwtQR2qCeqsrLcpDPhGJirMhB0DywSQaKICBHoKnKUdBoQErcbjh9Rdi7WmxgYzP7tQa2Bq4SqvxapY2kPqiW8bRd26/BPMYRPCapPZIXYCICICbpcYkGzE1mpws7Ywhm7nb9PNu+jwdvk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=WktLwMVC; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="WktLwMVC" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D1770C4CEF7; Mon, 23 Mar 2026 23:59:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774310400; bh=qJyAYAiz0wfqqJjBKxAwZyVPhPLmb0z+stL3H8W7gLA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WktLwMVCRwT//RKfGaOIGie0yC1L+3gfO2J4MiKAqc1VsIbigE8P9yyIgik6Gil4/ vkxEmDTQvVABhmOuqnVEEBaWE+8fjg0CDeP2TMP97kNnJQTe1peOZUakyEKB6KdfoV 3mWyIjfkhNfYczAKpzAix2J/Dcb3+mthcRIPVE2qB62TILoLSB0rJneC8d3NXPTHTH Nh2SZboIQNDovGcDkpflLA2gv0PS366BFGi34P2vo4ubM8JDtRkB5Spz1L3j63bffU byBhr7SB9hO9jum6QgyLJQiQBlQusp+sLW8iWzfg+9R/1L+LhdceZove1cSf7Py2hj qEQhk8f0q8kwA== Date: Mon, 23 Mar 2026 17:59:58 -0600 (MDT) From: Paul Walmsley To: Jisheng Zhang cc: Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] riscv: make runtime const not usable by modules In-Reply-To: <20260221023731.3476-1-jszhang@kernel.org> Message-ID: <94f9aad7-b31b-da59-46bc-0aed11941c3f@kernel.org> References: <20260221023731.3476-1-jszhang@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII On Sat, 21 Feb 2026, Jisheng Zhang wrote: > Similar as commit 284922f4c563 ("x86: uaccess: don't use runtime-const > rewriting in modules") does, make riscv's runtime const not usable by > modules too, to "make sure this doesn't get forgotten the next time > somebody wants to do runtime constant optimizations". The reason is > well explained in the above commit: "The runtime-const infrastructure > was never designed to handle the modular case, because the constant > fixup is only done at boot time for core kernel code." > > Signed-off-by: Jisheng Zhang Thanks, queued for v7.0-rc. - Paul