Changes in Makefile

8770a918 - selftests: vDSO: vdso_standalone_test_x86: Switch to nolibc

Wed, 26 Feb 2025 11:44:55 +0000

selftests: vDSO: vdso_standalone_test_x86: Switch to nolibcvdso_standalone_test_x86 provides its own ASM syscall wrappers and_start() implementation. The in-tree nolibc library already providesthis functionality for multiple architectures. By making use of nolibc,the standalone testcase can be built from the exact same codebase as thenon-standalone version.Signed-off-by: Thomas Weißschuh Signed-off-by: Thomas Gleixner Reviewed-by: Vincenzo Frascino Acked-by: Shuah Khan Link: https://lore.kernel.org/all/20250226-parse_vdso-nolibc-v2-16-28e14e031ed8@linutronix.de List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

c9fbaa87 - selftests: vDSO: parse_vdso: Use UAPI headers instead of libc headers

Wed, 26 Feb 2025 11:44:51 +0000

selftests: vDSO: parse_vdso: Use UAPI headers instead of libc headersTo allow the usage of parse_vdso.c together with a limited libc likenolibc, use the kernels own elf.h and auxvec.h headers.Signed-off-by: Thomas Weißschuh Signed-off-by: Thomas Gleixner Reviewed-by: Vincenzo Frascino Acked-by: Shuah Khan Link: https://lore.kernel.org/all/20250226-parse_vdso-nolibc-v2-12-28e14e031ed8@linutronix.de List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

fe6305cb - selftests: vDSO: unconditionally build getrandom test

Mon, 07 Oct 2024 21:45:57 +0000

selftests: vDSO: unconditionally build getrandom testRather than building on supported archs, build on all archs, and thenuse the presence of the symbol in the vDSO to either skip the test ormove forward with it.Note that this means that this test no longer checks whether the symbolwas correctly added to the kernel. But hopefully this will be clearenough to developers and we'll cross our fingers that symbols aren'tremoved by accident and not caught after this change.Signed-off-by: Jason A. Donenfeld Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

3b5992ea - selftests: vDSO: unconditionally build chacha test

Mon, 07 Oct 2024 21:45:56 +0000

selftests: vDSO: unconditionally build chacha testRather than using symlinks to find the vgetrandom-chacha.S file for eacharch, store this in a file that uses the compiler to determinearchitecture, and then make use of weak symbols to skip the test onarchitectures that don't provide the code.Signed-off-by: Jason A. Donenfeld Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

b920aa77 - s390/vdso: Wire up getrandom() vdso implementation

Fri, 13 Sep 2024 13:05:43 +0000

s390/vdso: Wire up getrandom() vdso implementationProvide the s390 specific vdso getrandom() architecture backend._vdso_rng_data required data is placed within the _vdso_data vvar page,by using a hardcoded offset larger than vdso_data.As required the chacha20 implementation does not write to the stack.The implementation follows more or less the arm64 implementations andmakes use of vector instructions. It has a fallback to the getrandom()system call for machines where the vector facility is not installed.The check if the vector facility is installed, as well as anoptimization for machines with the vector-enhancements facility 2, isimplemented with alternatives, avoiding runtime checks.Note that __kernel_getrandom() is implemented without the vdso userwrapper which would setup a stack frame for odd cases (aka very oldglibc variants) where the caller has not done that. All callers of__kernel_getrandom() are required to setup a stack frame, like the C ABIrequires it.The vdso testcases vdso_test_getrandom and vdso_test_chacha pass.Benchmark on a z16: $ ./vdso_test_getrandom bench-single vdso: 25000000 times in 0.493703559 seconds syscall: 25000000 times in 6.584025337 secondsSigned-off-by: Heiko Carstens Reviewed-by: Harald Freudenberger Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

53cee505 - powerpc/vdso: Wire up getrandom() vDSO implementation on VDSO32

Mon, 02 Sep 2024 19:17:21 +0000

powerpc/vdso: Wire up getrandom() vDSO implementation on VDSO32To be consistent with other VDSO functions, the function is called__kernel_getrandom()__arch_chacha20_blocks_nostack() fonction is implemented basicallywith 32 bits operations. It performs 4 QUARTERROUND operations inparallele. There are enough registers to avoid using the stack:On input: r3: output bytes r4: 32-byte key input r5: 8-byte counter input/output r6: number of 64-byte blocks to write to outputDuring operation: stack: pointer to counter (r5) and non-volatile registers (r14-131) r0: counter of blocks (initialised with r6) r4: Value '4' after key has been read, used for indexing r5-r12: key r14-r15: block counter r16-r31: chacha stateAt the end: r0, r6-r12: Zeroised r5, r14-r31: RestoredPerformance on powerpc 885 (using kernel selftest): ~# ./vdso_test_getrandom bench-single vdso: 25000000 times in 62.938002291 seconds libc: 25000000 times in 535.581916866 seconds syscall: 25000000 times in 531.525042806 secondsPerformance on powerpc 8321 (using kernel selftest): ~# ./vdso_test_getrandom bench-single vdso: 25000000 times in 16.899318858 seconds libc: 25000000 times in 131.050596522 seconds syscall: 25000000 times in 129.794790389 secondsThis first patch adds support for VDSO32. As selftests cannot easilybe generated only for VDSO32, and because the following patch bringssupport for VDSO64 anyway, this patch opts out all code in__arch_chacha20_blocks_nostack() so that vdso_test_chacha will notfail to compile and will not crash on PPC64/PPC64LE, allthough theselftest itself will fail.Signed-off-by: Christophe Leroy Acked-by: Michael Ellerman Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

8bc7c5e5 - selftests: vDSO: don't include generated headers for chacha test

Tue, 03 Sep 2024 12:52:45 +0000

selftests: vDSO: don't include generated headers for chacha testIt's not correct to use $(top_srcdir) for generated header files, forbuilds that are done out of tree via O=, and $(objtree) isn't valid inthe selftests context. Instead, just obviate the need for thesegenerated header files by defining empty stubs in tools/include, whichis the same thing that's done for rwlock.h.Reviewed-by: Adhemerval Zanella Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

712676ea - arm64: vDSO: Wire up getrandom() vDSO implementation

Tue, 03 Sep 2024 12:09:17 +0000

arm64: vDSO: Wire up getrandom() vDSO implementationHook up the generic vDSO implementation to the aarch64 vDSO data page.The _vdso_rng_data required data is placed within the _vdso_data vvarpage, by using a offset larger than the vdso_data.The vDSO function requires a ChaCha20 implementation that does not writeto the stack, and that can do an entire ChaCha20 permutation. The oneprovided uses NEON on the permute operation, with a fallback to thesyscall for chips that do not support AdvSIMD.This also passes the vdso_test_chacha test along withvdso_test_getrandom. The vdso_test_getrandom bench-single result onNeoverse-N1 shows: vdso: 25000000 times in 0.783884250 seconds libc: 25000000 times in 8.780275399 secondssyscall: 25000000 times in 8.786581518 secondsA small fixup to arch/arm64/include/asm/mman.h was required to avoidpulling kernel code into the vDSO, similar to what's already done inarch/arm64/include/asm/rwonce.h.Signed-off-by: Adhemerval Zanella Reviewed-by: Ard Biesheuvel Acked-by: Will Deacon Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

ecb8bd70 - selftests: vDSO: build tests with O2 optimization

Sun, 01 Sep 2024 17:24:03 +0000

selftests: vDSO: build tests with O2 optimizationWithout -O2, the generated code for testing chacha function is awful.GCC even implements rol32() as a function of 20 instructions instead ofjust using the rotlwi instruction. ~# time ./vdso_test_chacha TAP version 13 1..1 ok 1 chacha: PASS real 0m 37.16s user 0m 36.89s sys 0m 0.26sSeveral other selftests directory add -O2, and the kernel is alsoalways built with optimisation active. Do the same for vDSO selftests.With this patch the time is reduced by approximately 15%. ~# time ./vdso_test_chacha TAP version 13 1..1 ok 1 chacha: PASS real 0m 32.09s user 0m 31.86s sys 0m 0.22sSigned-off-by: Christophe Leroy Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

18efd0b1 - LoongArch: vDSO: Wire up getrandom() vDSO implementation

Sun, 01 Sep 2024 06:13:11 +0000

LoongArch: vDSO: Wire up getrandom() vDSO implementationHook up the generic vDSO implementation to the LoongArch vDSO data pageby providing the required __arch_chacha20_blocks_nostack,__arch_get_k_vdso_rng_data, and getrandom_syscall implementations. Alsowire up the selftests.Signed-off-by: Xi Ruoyao Acked-by: Huacai Chen Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

67a121ac - selftests: vDSO: fix cross build for getrandom and chacha tests

Sun, 01 Sep 2024 13:05:01 +0000

selftests: vDSO: fix cross build for getrandom and chacha testsUnlike the check for the standalone x86 test, the check for building thevDSO getrandom and chacaha tests looks at the architecture for the hostrather than the architecture for the target when deciding if they shouldbe built. Since the chacha test includes some assembler code this meansthat cross building with x86 as either the target or host is broken.There's also some additional complications, where ARCH can legitimatelybe either x86_64 or x86, but the source code we need to compile lives ina directory path containing arch/x86. The standard SRCARCH variablehandles that. And actually, all these variables and proper substitutionsare already described in tools/scripts/Makefile.arch, so just includethat to handle it.Similarly, ARCH=x86 can actually describe ARCH=x86_64,just with CONFIG_64BIT, so we can't rely on ARCH for selectingnon-32-bit tests. For that, check against $(ARCH)$(CONFIG_X86_32). Thiswon't help for people manually running this inside the vDSO selftestdirectory (which isn't really supported anyway and has problems onvarious archs), but it should work for builds of the kselftests, wherethe CONFIG_* variables are defined. On x86_64 machines,$(ARCH)$(CONFIG_X86_32) will evaluate to x86. On arm64 machines, it willevaluate to arm64. On 32-bit x86 machines, it will evaluate to x86y,which won't match the filter list.Reported-by: Mark Brown Reported-by: Christophe Leroy Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

7fe5b3e4 - selftests: vDSO: open code basic chacha instead of linking to libsodium

Wed, 28 Aug 2024 13:49:32 +0000

selftests: vDSO: open code basic chacha instead of linking to libsodiumLinking to libsodium makes building this test annoying in crosscompilation environments and is just way too much. Since this is just abasic correctness test, simply open code a simple, unoptimized, dumbchacha, rather than linking to libsodium.This also fixes a correctness issue on big endian systems. The kernel'srandom.c doesn't bother doing a le32_to_cpu operation on the randombytes that are passed as the key, and consequently neither doesvgetrandom-chacha.S. However, libsodium's chacha _does_ do this, sinceit takes the key as an array of bytes. This meant that the test wasbroken on big endian systems, which this commit rectifies.Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

b90eeff1 - selftests: vDSO: use KHDR_INCLUDES for UAPI headers for getrandom test

Wed, 28 Aug 2024 11:29:57 +0000

selftests: vDSO: use KHDR_INCLUDES for UAPI headers for getrandom testBuilding test_vdso_getrandom currently leads to following issue: In file included from /home/xry111/git-repos/linux/tools/include/linux/compiler_types.h:36, from /home/xry111/git-repos/linux/include/uapi/linux/stddef.h:5, from /home/xry111/git-repos/linux/include/uapi/linux/posix_types.h:5, from /usr/include/asm/sigcontext.h:12, from /usr/include/bits/sigcontext.h:30, from /usr/include/signal.h:301, from vdso_test_getrandom.c:14: /home/xry111/git-repos/linux/tools/include/linux/compiler-gcc.h:3:2: error: #error "Please don't include directly, include instead." 3 | #error "Please don't include directly, include instead." | ^~~~~It's because the compiler_types.h inclusion ininclude/uapi/linux/stddef.h is expected to be removed by theheader_install.sh script, as compiler_types.h shouldn't be used fromuser space.Add KHDR_INCLUDES before the existing include/uapi inclusion so thatusr/include takes precedence if it's populated.Signed-off-by: Xi Ruoyao Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

be915515 - selftests: vDSO: remove unnecessary command line defs from chacha test

Tue, 27 Aug 2024 14:52:36 +0000

selftests: vDSO: remove unnecessary command line defs from chacha testCONFIG_FUNCTION_ALIGNMENT=0 is no longer necessary and BULID_VDSO wasn'tspelled right while BUILD_VDSO isn't necessary, so just remove these.Reported-by: Adhemerval Zanella Netto Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

a5330eb3 - selftests: vDSO: separate LDLIBS from CFLAGS for libsodium

Tue, 27 Aug 2024 14:27:13 +0000

selftests: vDSO: separate LDLIBS from CFLAGS for libsodiumOn systems that set -Wl,--as-needed, putting the -lsodium in the wrongplace on the command line means we get a linker error: CC vdso_test_chacha /usr/bin/ld: /tmp/ccKpjnSM.o: in function `main': vdso_test_chacha.c:(.text+0x276): undefined reference to `crypto_stream_chacha20' collect2: error: ld returned 1 exit statusFix this by passing pkg-config's --libs output to the LDFLAGS fieldinstead of the CFLAGS field, as is customary.Reported-by: Adhemerval Zanella Netto Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

1e661b34 - selftests: vDSO: add --cflags for pkg-config command querying libsodium

Tue, 27 Aug 2024 13:20:15 +0000

selftests: vDSO: add --cflags for pkg-config command querying libsodiumWhen libsodium is installed into its own prefix, the --cflags output isneeded for the compiler to find libsodium headers.Signed-off-by: Xi Ruoyao Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

f8d92fc5 - selftests: vDSO: fix include order in build of test_vdso_chacha

Thu, 22 Aug 2024 07:13:23 +0000

selftests: vDSO: fix include order in build of test_vdso_chachaBuilding test_vdso_chacha currently leads to following issue: In file included from /home/chleroy/linux-powerpc/include/linux/limits.h:7, from /opt/powerpc64-e5500--glibc--stable-2024.02-1/powerpc64-buildroot-linux-gnu/sysroot/usr/include/bits/local_lim.h:38, from /opt/powerpc64-e5500--glibc--stable-2024.02-1/powerpc64-buildroot-linux-gnu/sysroot/usr/include/bits/posix1_lim.h:161, from /opt/powerpc64-e5500--glibc--stable-2024.02-1/powerpc64-buildroot-linux-gnu/sysroot/usr/include/limits.h:195, from /opt/powerpc64-e5500--glibc--stable-2024.02-1/lib/gcc/powerpc64-buildroot-linux-gnu/12.3.0/include-fixed/limits.h:203, from /opt/powerpc64-e5500--glibc--stable-2024.02-1/lib/gcc/powerpc64-buildroot-linux-gnu/12.3.0/include-fixed/syslimits.h:7, from /opt/powerpc64-e5500--glibc--stable-2024.02-1/lib/gcc/powerpc64-buildroot-linux-gnu/12.3.0/include-fixed/limits.h:34, from /tmp/sodium/usr/local/include/sodium/export.h:7, from /tmp/sodium/usr/local/include/sodium/crypto_stream_chacha20.h:14, from vdso_test_chacha.c:6: /opt/powerpc64-e5500--glibc--stable-2024.02-1/powerpc64-buildroot-linux-gnu/sysroot/usr/include/bits/xopen_lim.h:99:6: error: missing binary operator before token "(" 99 | # if INT_MAX == 32767 | ^~~~~~~ /opt/powerpc64-e5500--glibc--stable-2024.02-1/powerpc64-buildroot-linux-gnu/sysroot/usr/include/bits/xopen_lim.h:102:7: error: missing binary operator before token "(" 102 | # if INT_MAX == 2147483647 | ^~~~~~~ /opt/powerpc64-e5500--glibc--stable-2024.02-1/powerpc64-buildroot-linux-gnu/sysroot/usr/include/bits/xopen_lim.h:126:6: error: missing binary operator before token "(" 126 | # if LONG_MAX == 2147483647 | ^~~~~~~~This is due to kernel include/linux/limits.h being included instead oflibc's limits.h.This is because directory include/ is added through option -isystem soit goes prior to glibc's include directory.Replace -isystem by -idirafter.But this implies that now tools/include/linux/linkage.h is includedinstead of include/linux/linkage.h, so define a stub forSYM_FUNC_START() and SYM_FUNC_END().Signed-off-by: Christophe Leroy Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

20a9af05 - selftests: vDSO: don't hard-code location of vDSO sources

Thu, 22 Aug 2024 07:13:21 +0000

selftests: vDSO: don't hard-code location of vDSO sourcesArchitectures use different location for vDSO sources: arch/mips/vdso arch/sparc/vdso arch/arm64/kernel/vdso arch/riscv/kernel/vdso arch/csky/kernel/vdso arch/x86/um/vdso arch/x86/entry/vdso arch/powerpc/kernel/vdso arch/arm/vdso arch/loongarch/vdsoDon't hard-code vdso sources location in selftest Makefile. Insteadcreate a vdso/ symbolic link in tools/arch/$arch/ and update Makefileaccordingly.Signed-off-by: Christophe Leroy Signed-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

4920a259 - selftests/vDSO: add tests for vgetrandom

Sat, 06 Jul 2024 23:40:16 +0000

selftests/vDSO: add tests for vgetrandomThis adds two tests for vgetrandom. The first one, vdso_test_chacha,simply checks that the assembly implementation of chacha20 matches thatof libsodium, a basic sanity check that should catch most errors. Thesecond, vdso_test_getrandom, is a full "libc-like" implementation of theuserspace side of vgetrandom() support. It's meant to be used also asexample code for libcs that might be integrating this.Cc: linux-kselftest@vger.kernel.orgSigned-off-by: Jason A. Donenfeld List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile

66cde337 - selftests/vDSO: remove duplicate compiler invocations from Makefile

Fri, 05 Jul 2024 19:57:36 +0000

selftests/vDSO: remove duplicate compiler invocations from MakefileThe Makefile open-codes compiler invocations that ../lib.mk alreadyprovides.Avoid this by using a Make feature that allows setting per-targetvariables, which in this case are: CFLAGS and LDFLAGS. This approachgenerates the exact same compiler invocations as before, but removes allof the code duplication, along with the quirky mangled variable names.So now the Makefile is smaller, less unusual, and easier to read.The new dependencies are listed after including lib.mk, in order tolet lib.mk provide the first target ("all:"), and are grouped togetherwith their respective source file dependencies, for visual clarity.Signed-off-by: John Hubbard Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/vDSO/Makefile