Changes in 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/signal/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/signal/Makefile

beeac538 - selftests/powerpc: Add a test of sigreturning to an unaligned address

Tue, 21 Dec 2021 13:51:01 +0000

selftests/powerpc: Add a test of sigreturning to an unaligned addressAdd a test of sigreturning to an unaligned address (low two bits set).This should have no effect because the hardware will mask those bits.However it previously falsely triggered a warning whenCONFIG_PPC_RFI_SRR_DEBUG=y.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20211221135101.2085547-3-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile

a8968521 - selftests/powerpc: Add a test of sigreturning to the kernel

Thu, 09 Dec 2021 11:59:44 +0000

selftests/powerpc: Add a test of sigreturning to the kernelWe have a general signal fuzzer, sigfuz, which can modify the MSR & NIPbefore sigreturn. But the chance of it hitting a kernel address and alsoclearing MSR_PR is fairly slim.So add a specific test of sigreturn to a kernel address, both with andwithout attempting to clear MSR_PR (which the kernel must block).Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20211209115944.4062384-1-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile

4e0e45b0 - powerpc: Use trap metadata to prevent double restart rather than zeroing trap

Thu, 07 May 2020 12:13:32 +0000

powerpc: Use trap metadata to prevent double restart rather than zeroing trapIt's not very nice to zero trap for this, because then system calls nolonger have trap_is_syscall(regs) invariant, and we can't distinguishbetween sc and scv system calls (in a later patch).Take one last unused bit from the low bits of the pt_regs.trap wordfor this instead. There is not a really good reason why it should bein trap as opposed to another field, but trap has some concept offlags and it exists. Ideally I think we would move trap to 2-bytefield and have 2 more bytes available independently.Add a selftests case for this, which can be seen to fail iftrap_norestart() is changed to return false.Signed-off-by: Nicholas Piggin [mpe: Make them static inlines]Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200507121332.2233629-4-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/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/signal/Makefile

a0968a02 - selftests/powerpc: Add a test of sigreturn vs VDSO

Wed, 04 Mar 2020 11:04:02 +0000

selftests/powerpc: Add a test of sigreturn vs VDSOThere's two different paths through the sigreturn code, depending onwhether the VDSO is mapped or not. We recently discovered a bug in theunmapped case, because it's not commonly used these days.So add a test that sends itself a signal, then moves the VDSO, takesanother signal and finally unmaps the VDSO before sending itselfanother signal. That tests the standard signal path, the code thathandles the VDSO being moved, and also the signal path in the casewhere the VDSO is unmapped.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200304110402.6038-1-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile

83e367f9 - selftests/powerpc: Add a signal fuzzer selftest

Thu, 17 Jan 2019 17:01:54 +0000

selftests/powerpc: Add a signal fuzzer selftestThis is a new selftest that raises SIGUSR1 signals and handles it in aset of different ways, trying to create different scenario for testingpurpose.This test works raising a signal and calling sigreturn interleavedwith TM operations, as starting, suspending and terminating atransaction. The test depends on random numbers, and, based on them,it sets different TM states.Other than that, the test fills out the user context struct that ispassed to the sigreturn system call with random data, in order to makesure that the signal handler syscall can handle different and invalidstates properly.This selftest has command line parameters to control what kind oftests the user wants to run, as for example, if a transaction shouldbe started prior to signal being raised, or, after the signal beingraised and before the sigreturn. If no parameter is given, the defaultis enabling all options.This test does not check if the user context is being read and setproperly by the kernel. Its purpose, at this time, is basicallyguaranteeing that the kernel does not crash on invalid scenarios.Signed-off-by: Breno Leitao Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile

27825349 - selftests/powerpc/signal: Fix out-of-tree build

Mon, 29 Oct 2018 11:23:50 +0000

selftests/powerpc/signal: Fix out-of-tree buildWe should use TEST_GEN_PROGS, not TEST_PROGS. That tells the selftestsmakefile (lib.mk) that those tests are generated (built), and so itadds the $(OUTPUT) prefix for us, making the out-of-tree build workcorrectly.It also means we don't need our own clean rule, lib.mk does it.We also have to update the signal_tm rule to use $(OUTPUT).Signed-off-by: Joel Stanley Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile

58cfbac2 - Revert "selftests/powerpc: Fix out-of-tree build errors"

Thu, 25 Oct 2018 17:24:15 +0000

Revert "selftests/powerpc: Fix out-of-tree build errors"This reverts commit d8a2fe29d3c97038c8efcc328d5e7940c5310565.That commit, by me, fixed the out of tree build errors by causing someof the tests not to build at all. List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile

d8a2fe29 - selftests/powerpc: Fix out-of-tree build errors

Thu, 18 Oct 2018 13:11:33 +0000

selftests/powerpc: Fix out-of-tree build errorsSome of our Makefiles don't do the right thing when building theselftests with O=, fix them up.Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/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/signal/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/signal/Makefile

ef186331 - selftests/powerpc: Check that signals always get delivered

Fri, 23 Sep 2016 06:18:19 +0000

selftests/powerpc: Check that signals always get deliveredSigned-off-by: Cyril Bur Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/signal/Makefile