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

d3cf1662 - selftests/powerpc: Make dd output quiet

Tue, 28 Feb 2023 00:07:09 +0000

selftests/powerpc: Make dd output quietdd logs info to stderr by default. This info is pointless in theselftests and makes legitimate issues harder to spot.Pass the option to silence the info logs. Actual errors would still beprinted.Signed-off-by: Benjamin Gray Signed-off-by: Michael Ellerman Link: https://msgid.link/20230228000709.124727-4-bgray@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

98acee3f - selftests/powerpc: Add a test for execute-only memory

Wed, 17 Aug 2022 05:06:40 +0000

selftests/powerpc: Add a test for execute-only memoryThis selftest is designed to cover execute-only protectionson the Radix MMU but will also work with Hash.The tests are based on those found in pkey_exec_test with modificationsto use the generic mprotect() instead of the pkey variants.Signed-off-by: Nicholas Miehlbradt Signed-off-by: Russell Currey Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220817050640.406017-2-ruscur@russell.cc List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

e96a76ee - selftests/powerpc: Add a test of 4PB SLB handling

Thu, 17 Mar 2022 14:39:25 +0000

selftests/powerpc: Add a test of 4PB SLB handlingAdd a test for a bug we had in the 4PB address space SLB handling. Itwas fixed in commit 4c2de74cc869 ("powerpc/64: Interrupts save PPR onstack rather than thread_struct").Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220317143925.1030447-1-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

29e3ea8c - selftests/powerpc: Test for spurious kernel memory faults on radix

Mon, 08 Feb 2021 03:29:57 +0000

selftests/powerpc: Test for spurious kernel memory faults on radixPreviously when mapping kernel memory on radix, no ptesync wasincluded which would periodically lead to unhandled spurious faults.Mapping kernel memory is used when code patching with Strict RWXenabled. As suggested by Chris Riedl, turning ftrace on and off does alarge amount of code patching so is a convenient way to see this kindof fault.Add a selftest to try and trigger this kind of a spurious fault. Ittests for 30 seconds which is usually long enough for the issue toshow up.Signed-off-by: Jordan Niethe [mpe: Rename it to better reflect what it does, rather than the symptom]Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20210208032957.1232102-2-jniethe5@gmail.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

12564485 - Revert "powerpc/64s: Remove PROT_SAO support"

Fri, 21 Aug 2020 18:55:56 +0000

Revert "powerpc/64s: Remove PROT_SAO support"This reverts commit 5c9fa16e8abd342ce04dc830c1ebb2a03abf6c05.Since PROT_SAO can still be useful for certain classes of software,reintroduce it. Concerns about guest migration for LPARs using SAOwill be addressed next.Signed-off-by: Shawn Anastasio Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200821185558.35561-2-shawn@anastas.io List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

c9938a9d - selftests/powerpc: Add test of stack expansion logic

Fri, 24 Jul 2020 09:25:24 +0000

selftests/powerpc: Add test of stack expansion logicWe have custom stack expansion checks that it turns out are extremelybadly tested and contain bugs, surprise. So add some tests thatexercise the code and capture the current boundary conditions.The signal test currently fails on 64-bit kernels because the 2048byte allowance for the signal frame is too small, we will fix that ina subsequent patch.Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200724092528.1578671-1-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

c27f2fd1 - selftests/powerpc: Add test for pkey siginfo verification

Mon, 27 Jul 2020 04:00:40 +0000

selftests/powerpc: Add test for pkey siginfo verificationCommit c46241a370a61 ("powerpc/pkeys: Check vma beforereturning key fault error to the user") fixes a bug whichcauses the kernel to set the wrong pkey in siginfo when apkey fault occurs after two competing threads that haveallocated different pkeys, one fully permissive and theother restrictive, attempt to protect a common page at thesame time. This adds a test to detect the bug.Signed-off-by: Sandipan Das Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/ce40b6ee270bda52e8f4088578ed2faf7d1d509a.1595821792.git.sandipan@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

5c9fa16e - powerpc/64s: Remove PROT_SAO support

Fri, 03 Jul 2020 01:19:57 +0000

powerpc/64s: Remove PROT_SAO supportISA v3.1 does not support the SAO storage control attribute required toimplement PROT_SAO. PROT_SAO was used by specialised system software(Lx86) that has been discontinued for about 7 years, and is not thoughtto be used elsewhere, so removal should not cause problems.We rather remove it than keep support for older processors, becauselive migrating guest partitions to newer processors may not be possibleif SAO is in use (or worse allowed with silent races).- PROT_SAO stays in the uapi header so code using it would still build.- arch_validate_prot() is removed, the generic version rejects PROT_SAO so applications would get a failure at mmap() time.Signed-off-by: Nicholas Piggin [mpe: Drop KVM change for the time being]Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200703011958.1166620-3-npiggin@gmail.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

1addb644 - selftests/powerpc: Add test for execute-disabled pkeys

Thu, 04 Jun 2020 12:56:10 +0000

selftests/powerpc: Add test for execute-disabled pkeysApart from read and write access, memory protection keys canalso be used for restricting execute permission of pages onpowerpc. This adds a test to verify if the feature works asexpected.Signed-off-by: Sandipan Das Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200604125610.649668-4-sandipan@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

c405b738 - selftests/powerpc: Move Hash MMU check to utilities

Thu, 04 Jun 2020 12:56:09 +0000

selftests/powerpc: Move Hash MMU check to utilitiesThis moves a function to test if the MMU is in Hash modeunder the generic test utilities.Signed-off-by: Sandipan Das Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200604125610.649668-3-sandipan@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

5eb7cfb3 - selftests/powerpc: Add a test of bad (out-of-range) accesses

Mon, 20 May 2019 10:20:51 +0000

selftests/powerpc: Add a test of bad (out-of-range) accessesUserspace isn't allowed to access certain address ranges, make sure weactually test that to at least some degree.This would have caught the recent bug where the SLB fault handler wasincorrectly called on an out-of-range access when using the Radix MMU.It also would have caught the bug we had in get_region_id() where wewere inserting SLB entries for bad addresses.Signed-off-by: Michael Ellerman Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190520102051.12103-1-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

93cad5f7 - selftests/powerpc: Add test case for tlbie vs mtpidr ordering issue

Tue, 24 Sep 2019 03:52:54 +0000

selftests/powerpc: Add test case for tlbie vs mtpidr ordering issueSigned-off-by: Aneesh Kumar K.V [mpe: Some minor fixes to make it build]Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190924035254.24612-4-aneesh.kumar@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

16391bfc - selftests/powerpc: Add test of fork with mapping above 512TB

Thu, 13 Jun 2019 02:07:59 +0000

selftests/powerpc: Add test of fork with mapping above 512TBThis tests that when a process with a mapping above 512TB forks wecorrectly separate the parent and child address spaces. This exercisesthe bug in the context id handling fixed in the previous commit.Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/Makefile

b7683fc6 - selftests/powerpc: Add a test of wild bctr

Tue, 24 Jul 2018 05:53:22 +0000

selftests/powerpc: Add a test of wild bctrThis tests that a bctr (Branch to counter and link), ie. a functioncall, to a wildly out-of-bounds address is handled correctly.Some old kernel versions didn't handle it correctly, see eg: "powerpc/slb: Force a full SLB flush when we insert for a bad EA" https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/157397.htmlSigned-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/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/mm/Makefile

6ed36158 - selftests/powerpc: Add a test of SEGV error behaviour

Tue, 02 Jan 2018 10:37:36 +0000

selftests/powerpc: Add a test of SEGV error behaviourAdd a test case of the error code reported when we take a SEGV on amapped but inaccessible area. We broke this recently.Based on a test case from John Sperbeck .Acked-by: John Sperbeck Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/mm/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/mm/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/mm/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/mm/Makefile