Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>
Cc: shuah@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
	 aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-kernel@vger.kernel.org,  linux-kselftest@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] selftests: riscv: Add README for RISC-V KSelfTest
Date: Tue, 19 Aug 2025 13:34:04 -0500	[thread overview]
Message-ID: <20250819-28695c586656c926fdfd0468@orel> (raw)
In-Reply-To: <20250815180724.14459-1-reddybalavignesh9979@gmail.com>

On Fri, Aug 15, 2025 at 11:37:24PM +0530, Bala-Vignesh-Reddy wrote:
> Add a README file for RISC-V specific kernel selftests under
> tools/testing/selftests/riscv/. This mirrors the existing README
> for arm64, providing clear guidance on how the tests are architecture
> specific and skipped on non-riscv systems. It also includes
> standard make commands for building, running and installing the
> tests, along with a reference to general kselftest documentation.
> 
> Signed-off-by: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>
> ---
>  tools/testing/selftests/riscv/README | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
>  create mode 100644 tools/testing/selftests/riscv/README
> 
> diff --git a/tools/testing/selftests/riscv/README b/tools/testing/selftests/riscv/README
> new file mode 100644
> index 000000000000..443da395da68
> --- /dev/null
> +++ b/tools/testing/selftests/riscv/README
> @@ -0,0 +1,24 @@
> +KSelfTest RISC-V
> +================
> +
> +- These tests are riscv specific and so not built or run but just skipped
> +  completely when env-variable ARCH is found to be different than 'riscv'.
> +
> +- Holding true the above, RISC-V KSFT tests can be run within the
> +  KSelfTest framework using standard Linux top-level-makefile targets:
> +
> +      $ make TARGETS=riscv kselftest-clean
> +      $ make TARGETS=riscv kselftest
> +
> +      or
> +
> +      $ make -C tools/testing/selftests TARGETS=riscv \
> +		INSTALL_PATH=<your-installation-path> install
> +
> +      or, alternatively, only specific riscv/ subtargets can be picked:
> +
> +      $ make -C tools/testing/selftests TARGETS=riscv RISCV_SUBTARGETS="mm vector" \
> +		INSTALL_PATH=<your-installation-path> install
> +
> +   Further details on building and running KSFT can be found in:
> +     Documentation/dev-tools/kselftest.rst
> -- 
> 2.43.0
>

Reviewed-by: Andrew Jones <ajones@ventanamicro.com>

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

  reply	other threads:[~2025-08-19 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 18:07 [PATCH] selftests: riscv: Add README for RISC-V KSelfTest Bala-Vignesh-Reddy
2025-08-19 18:34 ` Andrew Jones [this message]
2025-09-19  1:32 ` 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=20250819-28695c586656c926fdfd0468@orel \
    --to=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=reddybalavignesh9979@gmail.com \
    --cc=shuah@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