Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Feng Jiang <jiangfeng@kylinos.cn>
To: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, kees@kernel.org, andy@kernel.org,
	jiangfeng@kylinos.cn, ebiggers@kernel.org,
	martin.petersen@oracle.com, Jason@zx2c4.com,
	conor.dooley@microchip.com, samuel.holland@sifive.com,
	charlie@rivosinc.com, ajones@ventanamicro.com, nathan@kernel.org,
	linus.walleij@linaro.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: [PATCH 0/5] riscv: optimize string functions and add kunit tests
Date: Wed,  7 Jan 2026 10:35:12 +0800	[thread overview]
Message-ID: <20260107023517.46840-1-jiangfeng@kylinos.cn> (raw)

This series introduces optimized assembly implementations for several 
string functions on the RISC-V architecture (strnlen, strchr, and strrchr). 
To ensure correctness and prevent regressions, it also extends the 
string_kunit test suite with new cases.

The patchset is organized as follows:
- Patches 1-2: Enhance lib/string_kunit.c with new test cases for 
  strlen and strnlen to establish a baseline for verification.
- Patches 3-5: Provide the RISC-V specific optimized implementations 
  for strnlen, strchr, and strrchr.

Testing:
All patches have been verified using the KUnit framework on QEMU 
virt machine (riscv64). All string-related tests passed.

Changes:
- v1: Initial submission.

---

Feng Jiang (5):
  lib/string_kunit: add test case for strlen
  lib/string_kunit: add test case for strnlen
  riscv: lib: add strnlen implementation
  riscv: lib: add strchr implementation
  riscv: lib: add strrchr implementation

 arch/riscv/include/asm/string.h |   9 ++
 arch/riscv/lib/Makefile         |   3 +
 arch/riscv/lib/strchr.S         |  35 +++++++
 arch/riscv/lib/strnlen.S        | 164 ++++++++++++++++++++++++++++++++
 arch/riscv/lib/strrchr.S        |  37 +++++++
 arch/riscv/purgatory/Makefile   |  11 ++-
 lib/tests/string_kunit.c        |  53 +++++++++++
 7 files changed, 311 insertions(+), 1 deletion(-)
 create mode 100644 arch/riscv/lib/strchr.S
 create mode 100644 arch/riscv/lib/strnlen.S
 create mode 100644 arch/riscv/lib/strrchr.S

-- 
2.25.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2026-01-07  2:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07  2:35 Feng Jiang [this message]
2026-01-07  2:35 ` [PATCH 1/5] lib/string_kunit: add test case for strlen Feng Jiang
2026-01-07 11:48   ` Andy Shevchenko
2026-01-07  2:35 ` [PATCH 2/5] lib/string_kunit: add test case for strnlen Feng Jiang
2026-01-07 11:56   ` Andy Shevchenko
2026-01-08  6:53     ` Feng Jiang
2026-01-08  7:26       ` Andy Shevchenko
2026-01-08 10:00         ` Feng Jiang
2026-01-08 10:42           ` Andy Shevchenko
2026-01-07  2:35 ` [PATCH 3/5] riscv: lib: add strnlen implementation Feng Jiang
2026-01-07  2:35 ` [PATCH 4/5] riscv: lib: add strchr implementation Feng Jiang
2026-01-07  2:35 ` [PATCH 5/5] riscv: lib: add strrchr implementation Feng Jiang

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=20260107023517.46840-1-jiangfeng@kylinos.cn \
    --to=jiangfeng@kylinos.cn \
    --cc=Jason@zx2c4.com \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=andy@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=ebiggers@kernel.org \
    --cc=kees@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    --cc=nathan@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=samuel.holland@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