From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <guoren@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <alex@ghiti.fr>, <charlie@rivosinc.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv: pgtable: Cleanup useless VA_USER_XXX definitions
Date: Mon, 1 Dec 2025 17:27:52 +0800 [thread overview]
Message-ID: <812ce4ef-16cc-6c75-f1b0-ee128dcf45f1@huawei.com> (raw)
In-Reply-To: <20251201005850.702569-1-guoren@kernel.org>
On 2025/12/1 8:58, guoren@kernel.org wrote:
> From: "Guo Ren (Alibaba DAMO Academy)" <guoren@kernel.org>
>
> These marcos are not used after commit b5b4287accd7 ("riscv: mm: Use
> hint address in mmap if available"). Cleanup VA_USER_XXX definitions
> in asm/pgtable.h.
>
> Fixes: b5b4287accd7 ("riscv: mm: Use hint address in mmap if available")
> Signed-off-by: Guo Ren (Alibaba DAMO Academy) <guoren@kernel.org>
> ---
> arch/riscv/include/asm/pgtable.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/riscv/include/asm/pgtable.h b/arch/riscv/include/asm/pgtable.h
> index 5a08eb5fe99f..30d1ea93dde3 100644
> --- a/arch/riscv/include/asm/pgtable.h
> +++ b/arch/riscv/include/asm/pgtable.h
> @@ -124,10 +124,6 @@
> #ifdef CONFIG_64BIT
> #include <asm/pgtable-64.h>
>
> -#define VA_USER_SV39 (UL(1) << (VA_BITS_SV39 - 1))
> -#define VA_USER_SV48 (UL(1) << (VA_BITS_SV48 - 1))
> -#define VA_USER_SV57 (UL(1) << (VA_BITS_SV57 - 1))
Reviewed-by: Jinjie Ruan <ruanjinjie@huawei.com>
> -
> #define MMAP_VA_BITS_64 ((VA_BITS >= VA_BITS_SV48) ? VA_BITS_SV48 : VA_BITS)
> #define MMAP_MIN_VA_BITS_64 (VA_BITS_SV39)
> #define MMAP_VA_BITS (is_compat_task() ? VA_BITS_SV32 : MMAP_VA_BITS_64)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-01 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 0:58 [PATCH] riscv: pgtable: Cleanup useless VA_USER_XXX definitions guoren
2025-12-01 9:27 ` Jinjie Ruan [this message]
2026-01-06 0:50 ` Paul Walmsley
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=812ce4ef-16cc-6c75-f1b0-ee128dcf45f1@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=alex@ghiti.fr \
--cc=charlie@rivosinc.com \
--cc=guoren@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