Changes in Makefile

dda32e37 - selftests/powerpc: Install tests in sub-directories

Mon, 22 Apr 2024 13:34:53 +0000

selftests/powerpc: Install tests in sub-directoriesThe sources for the powerpc selftests are arranged into sub-directories.However when the tests are built and installed, the sub-directories aresquashed, losing the structure.For example, with the current code the result of installing the selftests is: $ tree tools/testing/selftests/kselftest_install tools/testing/selftests/kselftest_install ├── kselftest │ ├── ktap_helpers.sh │ ├── module.sh │ ├── prefix.pl │ └── runner.sh ├── kselftest-list.txt ├── powerpc │ ├── alignment_handler │ ├── attr_test │ ├── back_to_back_ebbs_test │ ├── bad_accesses │ ├── bhrb_filter_map_test │ ├── bhrb_no_crash_wo_pmu_test │ ├── blacklisted_events_test │ ├── cache_shape │ ├── close_clears_pmcc_test │ ├── context_switch │ ├── copy_first_unaligned ... │ ├── settings ... │ └── wild_bctr └── run_kselftest.shAll the powerpc tests are squashed into the single powerpc directory. Inparticular, note that there is a single `settings` file, even thoughthere are multiple settings files in the powerpc selftest sources. Oneof the settings files ends up installed, depending on install order,even if they have different contents.Similarly if there were two tests with the same name in differentsub-directories they would clobber each other.Fix it by replicating the directory structure of the source tree intothe install directory. The result being for example: $ tree tools/testing/selftests/kselftest_install tools/testing/selftests/kselftest_install ├── kselftest │ ├── ktap_helpers.sh │ ├── module.sh │ ├── prefix.pl │ └── runner.sh ├── kselftest-list.txt ├── powerpc │ ├── alignment │ │ ├── alignment_handler │ │ └── copy_first_unaligned │ ├── benchmarks │ │ ├── context_switch │ │ ├── exec_target │ │ ├── fork │ │ ├── futex_bench │ │ ├── gettimeofday │ │ ├── mmap_bench │ │ ├── null_syscall │ │ └── settings ... │ ├── eeh │ │ ├── eeh-basic.sh │ │ ├── eeh-functions.sh │ │ └── settings ... │ └── vphn │ └── test-vphn └── run_kselftest.shNote multiple settings files in different sub-directories.This change also has the effect of changing the names of the tests fromthe point of view of the kselftest runner. Before the tests are namedeg: powerpc:copy_first_unaligned powerpc:cache_shape powerpc:reg_access_testAfter, the test collection names include the sub-directory: powerpc/alignment:copy_first_unaligned powerpc/cache_shape:cache_shape powerpc/pmu/ebb:reg_access_testThat means whereas previously all powerpc tests could be run with: $ ./run_kselftest.sh -c powerpcAfter the change it's necessary to pass a regex that matches all powerpcentries, eg: $ ./run_kselftest.sh -c "powerpc.*"The latter form also works before and after the change.Signed-off-by: Michael Ellerman Link: https://msgid.link/20240422133453.1793988-2-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/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/Makefile

76b2ec3f - powerpc/selftests: Add test for papr-sysparm

Tue, 12 Dec 2023 17:02:00 +0000

powerpc/selftests: Add test for papr-sysparmConsistently testing system parameter access is a bit difficult bynature -- the set of parameters available depends on the model andsystem configuration, and updating a parameter should be considered adestructive operation reserved for the admin.So we validate some of the error paths and retrieve the SPLPARcharacteristics string, but not much else.Signed-off-by: Nathan Lynch Signed-off-by: Michael Ellerman Link: https://msgid.link/20231212-papr-sys_rtas-vs-lockdown-v6-13-e9eafd0c8c6c@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

9118c5d3 - powerpc/selftests: Add test for papr-vpd

Tue, 12 Dec 2023 17:01:59 +0000

powerpc/selftests: Add test for papr-vpdAdd selftests for /dev/papr-vpd, exercising the common expected usecases:* Retrieve all VPD by passing an empty location code.* Retrieve the "system VPD" by passing a location code derived from DT root node properties, as done by the vpdupdate command.The tests also verify that certain intended properties of the driverhold:* Passing an unterminated location code to PAPR_VPD_CREATE_HANDLE gets EINVAL.* Passing a NULL location code pointer to PAPR_VPD_CREATE_HANDLE gets EFAULT.* Closing the device node without first issuing a PAPR_VPD_CREATE_HANDLE command to it succeeds.* Releasing a handle without first consuming any data from it succeeds.* Re-reading the contents of a handle returns the same data as the first time.Some minimal validation of the returned data is performed.The tests are skipped on systems where the papr-vpd driver does notinitialize, making this useful only on PowerVM LPARs at this point.Signed-off-by: Nathan Lynch Signed-off-by: Michael Ellerman Link: https://msgid.link/20231212-papr-sys_rtas-vs-lockdown-v6-12-e9eafd0c8c6c@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

58b33e78 - selftests/powerpc: Fix emit_tests to work with run_kselftest.sh

Thu, 21 Sep 2023 07:26:10 +0000

selftests/powerpc: Fix emit_tests to work with run_kselftest.shIn order to use run_kselftest.sh the list of tests must be emitted topopulate kselftest-list.txt.The powerpc Makefile is written to use EMIT_TESTS. But support forEMIT_TESTS was dropped in commit d4e59a536f50 ("selftests: Use runner.shfor emit targets"). Although prior to that commit a548de0fe8e1("selftests: lib.mk: add test execute bit check to EMIT_TESTS") hadalready broken run_kselftest.sh for powerpc due to the executable checkusing the wrong path.It can be fixed by replacing the EMIT_TESTS definitions with actualemit_tests rules in the powerpc Makefiles. This makes run_kselftest.shable to run powerpc tests: $ cd linux $ export ARCH=powerpc $ export CROSS_COMPILE=powerpc64le-linux-gnu- $ make headers $ make -j -C tools/testing/selftests install $ grep -c "^powerpc" tools/testing/selftests/kselftest_install/kselftest-list.txt 182Fixes: d4e59a536f50 ("selftests: Use runner.sh for emit targets")Signed-off-by: Michael Ellerman Link: https://msgid.link/20230921072623.828772-1-mpe@ellerman.id.au List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

bdb07f35 - selftests/powerpc/dexcr: Add hashst/hashchk test

Mon, 19 Jun 2023 07:36:27 +0000

selftests/powerpc/dexcr: Add hashst/hashchk testTest the kernel DEXCR[NPHIE] interface and hashchk exception handling.Introduces with it a DEXCR utils library for common DEXCR operations.Volatile is used to prevent the compiler optimising away the signaltests.Signed-off-by: Benjamin Gray Signed-off-by: Michael Ellerman Link: https://msgid.link/20230616034846.311705-11-bgray@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

4ecd0868 - selftests/powerpc: Pass make context to children

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

selftests/powerpc: Pass make context to childrenMake supports passing the 'jobserver' (parallel make support) to childinvocations of make when either 1. The target command uses $(MAKE) directly 2. The command starts with '+'This context is not passed through expansions that result in $(MAKE), sothe macros used in several places fail to pass on the jobserver context.Warnings are also raised by the child mentioning this.Prepend macros lines that invoke $(MAKE) with '+' to allow passing thejobserver context to these children.Signed-off-by: Benjamin Gray Signed-off-by: Michael Ellerman Link: https://msgid.link/20230228000709.124727-3-bgray@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

57201d65 - selftest/powerpc: Add PAPR sysfs attributes sniff test

Thu, 17 Feb 2022 10:53:21 +0000

selftest/powerpc: Add PAPR sysfs attributes sniff testInclude a testcase to check if the sysfs files for energy and frequencyrelated have its related attribute files exist and populatedSigned-off-by: Pratik R. Sampat Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220217105321.52941-3-psampat@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

0f4ef8a3 - selftests/powerpc: Add test for real address error handling

Fri, 07 Jan 2022 14:14:27 +0000

selftests/powerpc: Add test for real address error handlingAdd test for real address or control memory address accesserror handling, using NX-GZIP engine.The error is injected by accessing the control memory addressusing illegal instruction, on successful handling the processattempting to access control memory address using illegalinstruction receives SIGBUS.Signed-off-by: Ganesh Goudar Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20220107141428.67862-2-ganeshgr@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

647c734f - selftests/powerpc: Add NX-GZIP engine compress testcase

Mon, 20 Apr 2020 20:55:36 +0000

selftests/powerpc: Add NX-GZIP engine compress testcaseAdd a compression testcase for the powerpc NX-GZIP engine.Signed-off-by: Bulent Abali Signed-off-by: Raphael Moreira Zinsly Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200420205538.25181-4-rzinsly@linux.ibm.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

85d86c8a - selftests/powerpc: Add basic EEH selftest

Tue, 03 Sep 2019 10:16:05 +0000

selftests/powerpc: Add basic EEH selftestUse the new eeh_dev_check and eeh_dev_break interfaces to test EEHrecovery. Historically this has been done manually using platform specificEEH error injection facilities (e.g. via RTAS). However, documentation onhow to use these facilities is haphazard at best and non-existent at worstso it's hard to develop a cross-platform test.The new debugfs interfaces allow the kernel to handle the platform specificdetails so we can write a more generic set of sets. This patch adds themost basic of recovery tests where:a) Errors are injected and recovered from sequentially,b) Errors are not injected into PCI-PCI bridges, such as PCIe switches.c) Errors are only injected into device function zero.d) No errors are injected into Virtual Functions.a), b) and c) are largely due to limitations of Linux's EEH support. EEHrecovery is serialised in the EEH recovery thread which forces a).Similarly, multi-function PCI devices are almost always grouped into thesame PE so injecting an error on one function exercises the same codepaths. c) is because we currently more or less ignore PCI bridges duringrecovery and assume that the recovered topology will be the same as theoriginal.d) is due to the limits of the eeh_dev_break interface. With the currentimplementation we can't inject an error into a specific VF withoutpotentially causing additional errors on other VFs. Due to the serialisedrecovery process we might end up timing out waiting for another function torecover before the function of interest is recovered. The platform specificerror injection facilities are finer-grained and allow this capability, butdoing that requires working out how to use those facilities first.Basicly, it's better than nothing and it's a base to build on.Signed-off-by: Oliver O'Halloran Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190903101605.2890-15-oohall@gmail.com List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

d2bf7932 - selftests/powerpc: Add test to verify rfi flush across a system call

Mon, 21 May 2018 15:13:57 +0000

selftests/powerpc: Add test to verify rfi flush across a system callThis adds a test to verify proper functioning of the rfi flushcapability implemented to mitigate meltdown. The test works bymeasuring the number of L1d cache misses encountered while loadingdata from memory. Across a system call, since the L1d cache is flushedwhen rfi_flush is enabled, the number of cache misses is expected tobe relative to the number of cachelines corresponding to the databeing loaded.The current system setting is reflected via powerpc/rfi_flush underdebugfs (assumed to be /sys/kernel/debug/). This test verifies theexpected result with rfi_flush enabled as well as when it is disabled.Signed-off-by: Anton Blanchard Signed-off-by: Michael Ellerman Signed-off-by: Naveen N. Rao [mpe: Add SPDX tags, clang format, skip if the debugfs is missing, use __u64 and SANE_USERSPACE_TYPES to avoid printf() build errors.]Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

00c946a0 - selftests/powerpc: Remove redundant cp_abort test

Thu, 05 Oct 2017 23:48:57 +0000

selftests/powerpc: Remove redundant cp_abort testPaste on POWER9 only works on accelerators and no longer on realmemory. Hence this test is broken so remove it.Signed-off-by: Michael Neuling Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/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/Makefile

337f1e36 - selftests: powerpc: override clean in lib.mk to fix warnings

Fri, 21 Apr 2017 22:22:10 +0000

selftests: powerpc: override clean in lib.mk to fix warningsAdd override for lib.mk clean to fix the following warnings from cleantarget run.Makefile:63: warning: overriding recipe for target 'clean'../lib.mk:55: warning: ignoring old recipe for target 'clean'Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

2db2c250 - selftests/powerpc: Fix standalone powerpc build

Mon, 27 Mar 2017 04:11:44 +0000

selftests/powerpc: Fix standalone powerpc buildThe changes to enable building with a separate output directory, incommit a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT") brokebuilding the powerpc selftests on their own, eg: $ cd tools/testing/selftests/powerpc; makeIt was partially fixed in commit e53aff45c490 ("selftests: lib.mk Fixindividual test builds"), which defined OUTPUT for standalone tests. Butthat only defines OUTPUT within the Makefile, the value is not exportedso sub-shells can't see it. We could export OUTPUT, but it's actuallycleaner to just expand the value of OUTPUT before we invoke the shell.Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

3d2e03f8 - tools/testing/selftests/powerpc: remove redundant CFLAGS in Makefile: "-Wall -O2 -Wall" -> "-O2 -Wall"

Sun, 19 Feb 2017 08:19:20 +0000

tools/testing/selftests/powerpc: remove redundant CFLAGS in Makefile: "-Wall -O2 -Wall" -> "-O2 -Wall"There are repeated compiler flags "-Wall" in the Makefile.The redundant compiler flag appears to have been there from the introduction of the Makefile.Signed-off-by: Chijun Sima Signed-off-by: Jiri Kosina List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

b8b6ff01 - selftests/powerpc: Add cache_shape sniff test

Mon, 06 Feb 2017 10:13:28 +0000

selftests/powerpc: Add cache_shape sniff testThis is a very basic test of the new cache shape AUXV entries. All itdoes at the moment is look for the entries and error out if we don'tfind all the ones we expect. Primarily intended for folks bringing up anew chip to check that the cache info is making it all the way touserspace correctly.Signed-off-by: Michael Ellerman List of files: /linux-6.15/tools/testing/selftests/powerpc/Makefile

2e8ec87d - selftests/powerpc: Fix the clean rule since recent changes

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

selftests/powerpc: Fix the clean rule since recent changesThe clean rule is broken for the powerpc tests: make[1]: Entering directory 'tools/testing/selftests/powerpc' Makefile:63: warning: overriding recipe for target 'clean' ../lib.mk:51: warning: ignoring old recipe for target 'clean' /bin/sh: 3: Syntax error: end of file unexpected (expecting "done") Makefile:63: recipe for target 'clean' failedFixes: 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/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/Makefile