Changes in Makefile

8c9c01ce - selftests/powerpc: Allow building without static libc

Mon, 12 Aug 2024 09:41:52 +0000

selftests/powerpc: Allow building without static libcCurrently exec-target.c is linked statically with libc, which on Fedoraat least requires installing an additional package (glibc-static).If that package is not installed the build fails with: CC exec_target /usr/bin/ld: cannot find -lc: No such file or directory collect2: error: ld returned 1 exit statusAll exec_target.c does is call sys_exit, which can be done easily enoughusing inline assembly, and removes the requirement for a static libc tobe installed.Suggested-by: Michael Ellerman Signed-off-by: Madhavan Srinivasan Signed-off-by: Michael Ellerman Link: https://msgid.link/20240812094152.418586-1-maddy@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

108e5e68 - selftests/powerpc: make sub-folders buildable on their own

Thu, 29 Feb 2024 09:37:11 +0000

selftests/powerpc: make sub-folders buildable on their ownBuild breaks when executing make with run_tests for sub-foldersunder powerpc. This is because, CFLAGS and GIT_VERSION macros aredefined in Makefile of toplevel powerpc folder. make: Entering directory '/home/maddy/linux/tools/testing/selftests/powerpc/mm' gcc hugetlb_vs_thp_test.c ../harness.c ../utils.c -o /home/maddy/selftest_output//hugetlb_vs_thp_test hugetlb_vs_thp_test.c:6:10: fatal error: utils.h: No such file or directory 6 | #include "utils.h" | ^~~~~~~~~ compilation terminated.Fix this by adding the flags.mk in each sub-folder Makefile. Also removethe CFLAGS and GIT_VERSION macros from powerpc/ folder Makefile sincethe same is definied in flags.mkSigned-off-by: Madhavan Srinivasan Signed-off-by: Michael Ellerman Link: https://msgid.link/20240229093711.581230-3-maddy@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

37496845 - selftests/powerpc: Re-order *FLAGS to follow lib.mk

Thu, 29 Feb 2024 09:37:09 +0000

selftests/powerpc: Re-order *FLAGS to follow lib.mkIn some powerpc/ sub-folder Makefiles, CFLAGS are defined before lib.mkinclude. Clean it up by re-ordering the flags to follow after the mkinclude. This is needed to support sub-folders in powerpc/ buildable onits own.Signed-off-by: Madhavan Srinivasan Signed-off-by: Michael Ellerman Link: https://msgid.link/20240229093711.581230-1-maddy@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

850507f3 - selftests/powerpc: Turn off timeout setting for benchmarks, dscr, signal, tm

Wed, 18 Mar 2020 06:00:04 +0000

selftests/powerpc: Turn off timeout setting for benchmarks, dscr, signal, tmSome specific tests in powerpc can take longer than the default 45seconds that added in commit 852c8cbf34d3 ("selftests/kselftest/runner.sh:Add 45 second timeout per test") to run, the following test result wascollected across 2 Power8 nodes and 1 Power9 node in our pool: powerpc/benchmarks/futex_bench - 52s powerpc/dscr/dscr_sysfs_test - 116s powerpc/signal/signal_fuzzer - 88s powerpc/tm/tm_unavailable_test - 168s powerpc/tm/tm-poison - 240sThus they will fail with TIMEOUT error. Disable the timeout settingfor these sub-tests to allow them finish properly.https://bugs.launchpad.net/bugs/1864642Fixes: 852c8cbf34d3 ("selftests/kselftest/runner.sh: Add 45 second timeout per test")Signed-off-by: Po-Hsu Lin Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200318060004.10685-1-po-hsu.lin@canonical.com List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

7e0cf1c9 - selftests/powerpc: Fix Makefiles for headers_install change

Fri, 28 Sep 2018 04:53:18 +0000

selftests/powerpc: Fix Makefiles for headers_install changeCommit b2d35fa5fc80 ("selftests: add headers_install to lib.mk")introduced a requirement that Makefiles more than one level below theselftests directory need to define top_srcdir, but it didn't updateany of the powerpc Makefiles.This broke building all the powerpc selftests with eg: make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc' BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all make[2]: Entering directory '/src/linux/tools/testing/selftests/powerpc/alignment' ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory make[2]: *** No rule to make target '../../../../scripts/subarch.include'. make[2]: Failed to remake makefile '../../../../scripts/subarch.include'. Makefile:38: recipe for target 'alignment' failedFix it by setting top_srcdir in the affected Makefiles.Fixes: b2d35fa5fc80 ("selftests: add headers_install to lib.mk")Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

dd40c5b4 - selftests/powerpc: Add process creation benchmark

Tue, 06 Mar 2018 13:24:58 +0000

selftests/powerpc: Add process creation benchmarkSigned-off-by: Nicholas Piggin [mpe: Add SPDX, and fixup formatting]Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

68bd42d9 - selftests/powerpc: Fix remaining fallout from recent changes

Thu, 09 Feb 2017 08:56:30 +0000

selftests/powerpc: Fix remaining fallout from recent changesIn benchmarks we need to use $(TEST_GEN_PROGS) after we include lib.mk,because lib.mk does the substitution to add $(OUTPUT).In math the vmx and fpu names were typoed so they no longer matchedcorrectly, put back the 'v' and 'f'.In tm we need to substitute $(OUTPUT) into SIGNAL_CONTEXT_CHK_TESTS sothat the rule matches.In pmu there is an extraneous ':' on the end of $$BUILD_TARGET for theclean and install rules, which breaks the logic in the child Makefiles.Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

a8ba798b - selftests: enable O and KBUILD_OUTPUT

Tue, 29 Nov 2016 11:55:52 +0000

selftests: enable O and KBUILD_OUTPUTEnable O and KBUILD_OUTPUT for kselftest. User could compile kselftestto another directory by passing O or KBUILD_OUTPUT. And O is highpriority than KBUILD_OUTPUT.Signed-off-by: Bamvor Jian Zhang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

88baa78d - selftests: remove duplicated all and clean target

Tue, 29 Nov 2016 11:55:47 +0000

selftests: remove duplicated all and clean targetCurrently, kselftest use TEST_PROGS, TEST_PROGS_EXTENDED, TEST_FILES toindicate the test program, extended test program and test files. It iseasy to understand the purpose of these files. But mix of compiled anduncompiled files lead to duplicated "all" and "clean" targets.In order to remove the duplicated targets, introduce TEST_GEN_PROGS,TEST_GEN_PROGS_EXTENDED, TEST_GEN_FILES to indicate the compiledobjects.Also, the later patch will make use of TEST_GEN_XXX to redirect thesefiles to output directory indicated by KBUILD_OUTPUT or O.And add this changes to "Contributing new tests(details)" ofDocumentation/kselftest.txt.Signed-off-by: Bamvor Jian Zhang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

d8db9bc5 - selftests/powerpc: Add Anton's null_syscall benchmark to the selftests

Tue, 27 Sep 2016 14:10:16 +0000

selftests/powerpc: Add Anton's null_syscall benchmark to the selftestsPull in a version of Anton's null_syscall benchmark: http://ozlabs.org/~anton/junkcode/null_syscall.cSuggested-by: Michael Ellerman Signed-off-by: Anton Blanchard Signed-off-by: Rui Teng Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

0c63e8b7 - selftests/powerpc: Import Anton's mmap & futex micro benchmarks

Thu, 02 Jun 2016 12:02:01 +0000

selftests/powerpc: Import Anton's mmap & futex micro benchmarksThese are useful little loops for smoke testing performance.Signed-off-by: Anton Blanchard Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

f2418ae8 - selftests/powerpc: Fix generation of vector instructions/types in context_switch

Thu, 03 Mar 2016 23:06:40 +0000

selftests/powerpc: Fix generation of vector instructions/types in context_switchCurrently it doesn't appear the resulting binary actually uses anyAltivec or VSX instructions the solution is to explicitly tell GCC touse vector instructions and use vector types in the code.Part of this this issue can be GCC version specific:GCC 4.9.x is happy to use Altivec and VSX instructions if altivec.h isincludedi (and possibly if vector types are used), this also means that4.9.x will use VSX instructions even if only -maltivec is passed. It isalso possible that Altivec instructions will be used even without-maltivec or -mabi=altivec.GCC 5.2.x complains about the lack of -maltivec parameter if altivec.his included and will not use VSX unless -mvsx is present on commandline.GCC 5.3.0 has a regression that means __attribute__((__target__("no-vsx"))fails to build. A fix is targeted for 5.4.Furthermore LTO (Link Time Optimisation) doesn't play well with__attribute__((__target__("no-vsx")), LTO can cause GCC to forget aboutthe attribute and compile with VSX instructions regardless. Be wary whenenabling -flfo for this test.Signed-off-by: Cyril Bur Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

ea0c3217 - selftests/powerpc: Make context_switch do something with no args

Wed, 02 Dec 2015 09:44:10 +0000

selftests/powerpc: Make context_switch do something with no argsFor ease of use make the context_switch test do something useful whencalled with no arguments.Default to a 30 second run, using threads, doing yield, and use anyonline cpu. Make it print out what it's doing to avoid confusion.Signed-off-by: Michael Ellerman Acked-by: Anton Blanchard List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

00b7ec5c - selftests/powerpc: Import Anton's context_switch2 benchmark

Wed, 02 Dec 2015 09:44:09 +0000

selftests/powerpc: Import Anton's context_switch2 benchmarkThis gets referred to a lot in commit messages, so let's pull it intothe selftests.Almost vanilla from: http://ozlabs.org/~anton/junkcode/context_switch2.cSigned-off-by: Anton Blanchard Signed-off-by: Michael Ellerman Acked-by: Anton Blanchard List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile

d17475d9 - powerpc/selftest: Add gettimeofday() benchmark

Fri, 25 Sep 2015 04:01:39 +0000

powerpc/selftest: Add gettimeofday() benchmarkThis adds a benchmark directory to the powerpc selftests and adds agettimeofday() benchmark to it.Suggested-by: Michael Ellerman Signed-off-by: Michael Neuling Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/benchmarks/Makefile