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/ptrace/Makefile

58709f6f - selftests/powerpc/ptrace: Update ptrace-perf watchpoint selftest

Tue, 01 Aug 2023 01:17:43 +0000

selftests/powerpc/ptrace: Update ptrace-perf watchpoint selftestNow that ptrace and perf are no longer exclusive, update thetest to exercise interesting interactions.An assembly file is used for the children to allow precise instructionchoice and addresses, while avoiding any compiler quirks.Signed-off-by: Benjamin Gray Signed-off-by: Michael Ellerman Link: https://msgid.link/20230801011744.153973-7-bgray@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

4f11410b - selftests/powerpc: Fix incorrect kernel headers search path

Fri, 27 Jan 2023 13:57:42 +0000

selftests/powerpc: Fix incorrect kernel headers search pathUse $(KHDR_INCLUDES) as lookup path for kernel headers. This preventsbuilding against kernel headers from the build environment in scenarioswhere kernel headers are installed into a specific output directory(O=...).Cc: stable@vger.kernel.org # v5.18+Signed-off-by: Mathieu Desnoyers Acked-by: Shuah Khan Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20230127135755.79929-22-mathieu.desnoyers@efficios.com List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

611e3850 - selftests/powerpc/ptrace: Do more of ptrace-gpr in asm

Mon, 27 Jun 2022 14:02:36 +0000

selftests/powerpc/ptrace: Do more of ptrace-gpr in asmThe ptrace-gpr test includes some inline asm to load GPR and FPRregisters. It then goes back to C to wait for the parent to trace it andthen checks register contents.The split between inline asm and C is fragile, it relies on the compilernot using any non-volatile GPRs after the inline asm block. It alsorequires a very large and unwieldy inline asm block.So convert the logic to set registers, wait, and store registers to asingle asm function, meaning there's no window for the compiler tointervene.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220627140239.2464900-10-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

149a497d - selftests/powerpc/ptrace: Build the ptrace-gpr test as 32-bit when possible

Mon, 27 Jun 2022 14:02:35 +0000

selftests/powerpc/ptrace: Build the ptrace-gpr test as 32-bit when possibleThe ptrace-gpr test can now be built 32-bit, so do that if that's thecompiler default rather than forcing a 64-bit build.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220627140239.2464900-9-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

3c20a1d0 - selftests/powerpc/ptrace: Split CFLAGS better

Mon, 27 Jun 2022 14:02:29 +0000

selftests/powerpc/ptrace: Split CFLAGS betterCurrently all ptrace tests are built 64-bit and with TM enabled.Only the TM tests need TM enabled, so split those out into a separatevariable so that can be specified precisely.Split the rest of the tests into a variable, and add -m64 to CFLAGS forthose tests, so that in a subsequent patch some tests can be made tobuild 32-bit.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220627140239.2464900-3-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

cf4baafd - selftests/powerpc/ptrace: Set LOCAL_HDRS

Mon, 27 Jun 2022 14:02:28 +0000

selftests/powerpc/ptrace: Set LOCAL_HDRSSet LOCAL_HDRS so header changes cause rebuilds. The lib.mk logic addsall the headers in LOCAL_HDRS as dependencies, so there's no need toalso list them explicitly.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220627140239.2464900-2-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

290f7d8c - powerpc/selftests: Add selftest to test concurrent perf/ptrace events

Mon, 12 Apr 2021 11:22:18 +0000

powerpc/selftests: Add selftest to test concurrent perf/ptrace eventsptrace and perf watchpoints can't co-exists if their address rangeoverlaps. See commit 29da4f91c0c1 ("powerpc/watchpoint: Don't allowconcurrent perf and ptrace events") for more detail. Add selftestfor the same.Sample o/p: # ./ptrace-perf-hwbreak test: ptrace-perf-hwbreak tags: git_version:powerpc-5.8-7-118-g937fa174a15d-dirty perf cpu event -> ptrace thread event (Overlapping): Ok perf cpu event -> ptrace thread event (Non-overlapping): Ok perf thread event -> ptrace same thread event (Overlapping): Ok perf thread event -> ptrace same thread event (Non-overlapping): Ok perf thread event -> ptrace other thread event: Ok ptrace thread event -> perf kernel event: Ok ptrace thread event -> perf same thread event (Overlapping): Ok ptrace thread event -> perf same thread event (Non-overlapping): Ok ptrace thread event -> perf other thread event: Ok ptrace thread event -> perf cpu event (Overlapping): Ok ptrace thread event -> perf cpu event (Non-overlapping): Ok ptrace thread event -> perf same thread & cpu event (Overlapping): Ok ptrace thread event -> perf same thread & cpu event (Non-overlapping): Ok ptrace thread event -> perf other thread & cpu event: Ok success: ptrace-perf-hwbreakSigned-off-by: Ravi Bangoria Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20210412112218.128183-5-ravi.bangoria@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

c39b7908 - selftests/powerpc/ptrace: Fix out-of-tree build

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

selftests/powerpc/ptrace: 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 ptrace-pkey and core-pkey rules to use$(OUTPUT).Signed-off-by: Joel Stanley Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/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/ptrace/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/ptrace/Makefile

fc35ef12 - selftests/powerpc: New PTRACE_SYSEMU test

Thu, 20 Sep 2018 16:45:07 +0000

selftests/powerpc: New PTRACE_SYSEMU testThis patch adds a new test for the new PTRACE_SYSEMU ptrace request.This test also relies on PTRACE_GETREGS and PTRACE_SETREGS requests torun properly, since the trace instruction (gettid() syscall) is beingmodified at run-time (by PTRACE_SETREGS) and re-executed three times.PTRACE_GETREGS is being used to check that the registers are stillsane.This test basically creates a child process that executes syscallsand the parent process check if it is being traced appropriately. Theparent process guarantees that the SYSCALLs are being traced, withPTRACE_SYSEMU, and ptrace stops the child application before a syscall isexecuted. The way the tests validates it, is by guaranteeing that thesystem calls arguments, as argv[0] (r3) which is the same register thatwill have the syscall return value on powerpc, are not being corrupted onPTRACE_SYSEMU with a return value, i.e, it continues to have the currentarguments instead, meaning that the registers where not clobbered.This test is basically the same test for x86 located attools/testing/selftests/x86/ptrace_syscall.c, limited to test PTRACE_SYSEMUrequest, and ported to PowerPC.Signed-off-by: Breno Leitao Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/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/ptrace/Makefile

9c2d72d4 - selftests/powerpc: Add perf breakpoint test

Mon, 28 May 2018 23:22:38 +0000

selftests/powerpc: Add perf breakpoint testThis tests perf hardware breakpoints (ie PERF_TYPE_BREAKPOINT) onpowerpc.Signed-off-by: Michael Neuling Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

39b91dd6 - selftests/powerpc: Add core file test for Protection Key registers

Fri, 25 May 2018 02:11:45 +0000

selftests/powerpc: Add core file test for Protection Key registersThis test verifies that the AMR, IAMR and UAMOR are being written to aprocess' core file.Signed-off-by: Thiago Jung Bauermann [mpe: Simplify make rule]Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

1f7256e7 - selftests/powerpc: Add ptrace tests for Protection Key registers

Fri, 25 May 2018 02:11:44 +0000

selftests/powerpc: Add ptrace tests for Protection Key registersThis test exercises read and write access to the AMR, IAMR and UAMOR.Signed-off-by: Thiago Jung Bauermann [mpe: Simplify make rule]Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

9c2ddfe5 - selftests/powerpc: Add ptrace hw breakpoint test

Tue, 22 May 2018 06:14:27 +0000

selftests/powerpc: Add ptrace hw breakpoint testThis test the ptrace hw breakpoints via PTRACE_SET_DEBUGREG andPPC_PTRACE_SETHWDEBUG. This test was use to find the bugs fixed bythese recent commits: 4f7c06e26e powerpc/ptrace: Fix setting 512B aligned breakpoints with PTRACE_SET_DEBUGREG cd6ef7eebf powerpc/ptrace: Fix enforcement of DAWR constraintsSigned-off-by: Michael Neuling [mpe: Add SPDX tag, clang format it]Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/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/ptrace/Makefile

a3c01050 - selftests/powerpc: Force ptrace tests to build -fno-pie

Wed, 30 Aug 2017 10:45:12 +0000

selftests/powerpc: Force ptrace tests to build -fno-pieCurrently these tests won't build with a `--enable-default-pie`compiler as they require r30 to be clobbered. This givesan error: ptrace-tm-spd-gpr.c:41:2: error: PIC register clobbered by 'r30' in 'asm'This forces these tests to be built no-pie.Signed-off-by: Michael Neuling Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile

5bdac52f - selftests/powerpc: Add ptrace tests for TM SPR registers

Fri, 30 Sep 2016 02:33:02 +0000

selftests/powerpc: Add ptrace tests for TM SPR registersThis patch adds ptrace interface test for TM SPR registers. Thisalso adds ptrace interface based helper functions related to TMSPR registers access.Signed-off-by: Anshuman Khandual Signed-off-by: Simon Guo Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/ptrace/Makefile