From: Xiao Wang <xiao.w.wang@intel.com>
To: paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu
Cc: jerry.shih@sifive.com, nick.knight@sifive.com,
ajones@ventanamicro.com, bjorn@rivosinc.com,
andy.chiu@sifive.com, viro@zeniv.linux.org.uk,
cleger@rivosinc.com, alexghiti@rivosinc.com,
haicheng.li@intel.com, akira.tsukamoto@gmail.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Xiao Wang <xiao.w.wang@intel.com>
Subject: [PATCH] riscv: uaccess: Allow the last potential unrolled copy
Date: Wed, 13 Mar 2024 18:33:34 +0800 [thread overview]
Message-ID: <20240313103334.4036554-1-xiao.w.wang@intel.com> (raw)
When the dst buffer pointer points to the last accessible aligned addr, we
could still run another iteration of unrolled copy.
Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
---
arch/riscv/lib/uaccess.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/lib/uaccess.S b/arch/riscv/lib/uaccess.S
index 2e665f8f8fcc..1399d797d81b 100644
--- a/arch/riscv/lib/uaccess.S
+++ b/arch/riscv/lib/uaccess.S
@@ -103,7 +103,7 @@ SYM_FUNC_START(fallback_scalar_usercopy)
fixup REG_S t4, 7*SZREG(a0), 10f
addi a0, a0, 8*SZREG
addi a1, a1, 8*SZREG
- bltu a0, t0, 2b
+ bleu a0, t0, 2b
addi t0, t0, 8*SZREG /* revert to original value */
j .Lbyte_copy_tail
--
2.25.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-03-13 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 10:33 Xiao Wang [this message]
2024-05-03 12:16 ` [PATCH] riscv: uaccess: Allow the last potential unrolled copy Alexandre Ghiti
2024-05-03 12:19 ` Ben Dooks
2024-05-03 13:02 ` Alexandre Ghiti
2024-05-03 14:30 ` Ben Dooks
2024-05-06 7:53 ` Wang, Xiao W
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=20240313103334.4036554-1-xiao.w.wang@intel.com \
--to=xiao.w.wang@intel.com \
--cc=ajones@ventanamicro.com \
--cc=akira.tsukamoto@gmail.com \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=haicheng.li@intel.com \
--cc=jerry.shih@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nick.knight@sifive.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).