Changes in Makefile

4ed8b153 - selftests: memory-hotplug: delete RUN_TESTS and EMIT_TESTS overrides

Wed, 02 May 2018 02:20:55 +0000

selftests: memory-hotplug: delete RUN_TESTS and EMIT_TESTS overridesDelete RUN_TESTS and EMIT_TESTS overrides and use common defines inlib.mk. Common defines work after making the change the test to runwith ratio=2 as the default mode to be able to invoke the test withoutthe "-r 2" argument from the common RUN_TESTS and EMIT_TESTS.The run_full_tests target now calls the test with "-r 10".Signed-off-by: Shuah Khan (Samsung OSG) Reviewed-by: Anders Roxell Reviewed-by: Lei.Yang@windriver.comSigned-off-by: Shuah Khan (Samsung OSG) List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

ba004a29 - selftests: memory-hotplug: fix emit_tests regression

Thu, 01 Mar 2018 20:04:28 +0000

selftests: memory-hotplug: fix emit_tests regressionCommit 16c513b13477("selftests: memory-hotplug: silence test command echo")introduced regression in emit_tests and results in the followingfailure when selftests are installed and run. Fix it.Running tests in memory-hotplug========================================./run_kselftest.sh: line 121: @./mem-on-off-test.sh: No such file ordirectoryselftests: memory-hotplug [FAIL]Fixes: 16c513b13477 (selftests: memory-hotplug: silence test command echo")Reported-by: Naresh Kamboju Tested-by: Anders Roxell Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

16c513b1 - selftests: memory-hotplug: silence test command echo

Tue, 13 Feb 2018 17:45:57 +0000

selftests: memory-hotplug: silence test command echoSilence the following command being printed while running test../mem-on-off-test.sh -r 2 && echo "selftests: memory-hotplug [PASS]" ||echo "selftests: memory-hotplug [FAIL]"Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

d3611d72 - selftests: add missing test result status in memory-hotplug test

Tue, 17 Oct 2017 07:06:48 +0000

selftests: add missing test result status in memory-hotplug testit only prints FAIL status when test fails, but doesn't print PASSstatus when test pass,this patch is to add PASS status in the test log.Signed-off-by: Lei Yang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/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/memory-hotplug/Makefile

072264fe - selftests: Change memory on-off-test.sh name to be unique

Fri, 27 Mar 2015 16:07:33 +0000

selftests: Change memory on-off-test.sh name to be uniquecpu and memory hotplug scripts use the same name. Changememory on-off-test.sh to mem-on-off-test.sh.Signed-off-by: Shuah Khan Acked-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

32dcfba6 - selftests: Add install target

Wed, 11 Mar 2015 04:06:00 +0000

selftests: Add install targetThis adds make install support to selftests. The basic usage is:$ cd tools/testing/selftests$ make installThat installs into tools/testing/selftests/install, which can then becopied where ever necessary.The install destination is also configurable using eg:$ INSTALL_PATH=/mnt/selftests make installThe implementation uses two targets in the child makefiles. The first"install" is expected to install all files into $(INSTALL_PATH).The second, "emit_tests", is expected to emit the test instructions (ie.bash script) on stdout. Separating this from install means the childmakefiles need no knowledge of the location of the test script.Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

5e29a910 - selftests: Introduce minimal shared logic for running tests

Wed, 11 Mar 2015 04:05:59 +0000

selftests: Introduce minimal shared logic for running testsThis adds a Make include file which most selftests can then include toget the run_tests logic.On its own this has the advantage of some reduction in repetition, andalso means the pass/fail message is defined in fewer places.However the key advantage is it will allow us to implement install verysimply in a subsequent patch.The default implementation just executes each program in $(TEST_PROGS).We use a variable to hold the default implementation of $(RUN_TESTS)because that gives us a clean way to override it if necessary, ie. usingoverride. The mount, memory-hotplug and mqueue tests use that to providea different implementation.Tests are not run via /bin/bash, so if they are scripts they must beexecutable, we add a+x to several.Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

ddddda9b - tools: selftests - create a separate hotplug target for full range test

Wed, 02 Jul 2014 15:51:38 +0000

tools: selftests - create a separate hotplug target for full range testOn some systems, hot-plug tests could hang forever waiting for cpu andmemory to be ready to be offlined. A special hot-plug target is createdto run full range of hot-plug tests. In default mode, hot-plug tests runin safe mode with a limited scope. In limited mode, cpu-hotplug test isrun on a single cpu as opposed to all hotplug capable cpus, and memoryhotplug test is run on 2% of hotplug capable memory instead of 10%. Inaddition to the above change, cpu-hotplug is chnged to change processoraffinity to cpu 0 so it doesn't impact itself while the test runs.Signed-off-by: Shuah Khan Cc: Kees Cook Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Frederic Weisbecker Signed-off-by: Andrew Morton Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

4813d2e7 - tools: memory-hotplug fix unexpected operator error

Wed, 25 Jun 2014 21:31:37 +0000

tools: memory-hotplug fix unexpected operator erroron-off-test is a bash script and invoked from /bin/shThis results in the following error:./on-off-test.sh: 9: [: !=: unexpected operatorChanged Makefile to use bash instead.Signed-off-by: Shuah Khan Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

e98f7762 - tools: memory-hotplug fix unexpected operator error

Wed, 02 Jul 2014 22:22:36 +0000

tools: memory-hotplug fix unexpected operator erroron-off-test uses "$UID != 0" to test for root, but $UID is a constructspecific to bash. Using /bin/sh that isn't bash results in thefollowing error (due to the "$UID" part expanding to nothing): ./on-off-test.sh: 9: [: !=: unexpected operatorChange Makefile to use bash instead.Signed-off-by: Shuah Khan Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

9307c295 - tools/testing/selftests: don't assume the x bit is set on scripts

Wed, 03 Jul 2013 22:09:23 +0000

tools/testing/selftests: don't assume the x bit is set on scriptsThe x bit can easily get lost (patch(1) loses it, for example).Reported-by: Ramkumar Ramachandra Cc: Dave Young Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

aabccae6 - mem-hotplug selftests: print failure status instead of cause make error

Tue, 18 Dec 2012 00:04:45 +0000

mem-hotplug selftests: print failure status instead of cause make errorOriginal behavior: bash-4.1$ make -C memory-hotplug run_tests make: Entering directory `/home/dave/git/linux-2.6/tools/testing/selftests/memory-hotplug' ./on-off-test.sh make: execvp: ./on-off-test.sh: Permission denied make: *** [run_tests] Error 127 make: Leaving directory `/home/dave/git/linux-2.6/tools/testing/selftests/memory-hotplug'After applying the patch: bash-4.1$ make -C memory-hotplug run_tests make: Entering directory `/home/dave/git/linux-2.6/tools/testing/selftests/memory-hotplug' /bin/sh: ./on-off-test.sh: Permission denied memory-hotplug selftests: [FAIL] make: Leaving directory `/home/dave/git/linux-2.6/tools/testing/selftests/memory-hotplug'Signed-off-by: Dave Young Reviewed-by: Pekka Enberg Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile

d89dffa9 - fault-injection: add selftests for cpu and memory hotplug

Mon, 30 Jul 2012 21:43:17 +0000

fault-injection: add selftests for cpu and memory hotplugThis adds two selftests* tools/testing/selftests/cpu-hotplug/on-off-test.sh is testing scriptfor CPU hotplug1. Online all hot-pluggable CPUs2. Offline all hot-pluggable CPUs3. Online all hot-pluggable CPUs again4. Exit if cpu-notifier-error-inject.ko is not available5. Offline all hot-pluggable CPUs in preparation for testing6. Test CPU hot-add error handling by injecting notifier errors7. Online all hot-pluggable CPUs in preparation for testing8. Test CPU hot-remove error handling by injecting notifier errors* tools/testing/selftests/memory-hotplug/on-off-test.sh is doing thesimilar thing for memory hotplug.1. Online all hot-pluggable memory2. Offline 10% of hot-pluggable memory3. Online all hot-pluggable memory again4. Exit if memory-notifier-error-inject.ko is not available5. Offline 10% of hot-pluggable memory in preparation for testing6. Test memory hot-add error handling by injecting notifier errors7. Online all hot-pluggable memory in preparation for testing8. Test memory hot-remove error handling by injecting notifier errorsSigned-off-by: Akinobu Mita Suggested-by: Andrew Morton Cc: Pavel Machek Cc: "Rafael J. Wysocki" Cc: Greg KH Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Michael Ellerman Cc: Dave Jones Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/memory-hotplug/Makefile