mirror of
https://github.com/torvalds/linux.git
synced 2026-09-24 06:24:02 +02:00
2464ac8a6f
While the GCC and Clang compilers already define __ASSEMBLER__ automatically when compiling assembly code, __ASSEMBLY__ is a macro that only gets defined by the Makefiles in the kernel. This can be very confusing when switching between userspace and kernelspace coding, or when dealing with uapi headers that rather should use __ASSEMBLER__ instead. So let's standardize now on the __ASSEMBLER__ macro that is provided by the compilers. Signed-off-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> Link: https://patch.msgid.link/20260813075304.75988-1-thuth@redhat.com Signed-off-by: Paul Walmsley <pjw@kernel.org> |
||
|---|---|---|
| .. | ||
| abi | ||
| cfi | ||
| hwprobe | ||
| mm | ||
| sigreturn | ||
| vector | ||
| Makefile | ||
| README | ||
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