powerpc/pseries: Move VPHN constants into vphn.hThese don't have any particularly good reason to belong in lppaca.h,move them into their own header.Signed-off-by: Michael Ellerman <mpe@ellerman.
powerpc/pseries: Move VPHN constants into vphn.hThese don't have any particularly good reason to belong in lppaca.h,move them into their own header.Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>Link: https://msgid.link/20230823055317.751786-1-mpe@ellerman.id.au
show more ...
.gitignore: add SPDX License IdentifierAdd SPDX License Identifier to all .gitignore files.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfou
.gitignore: add SPDX License IdentifierAdd SPDX License Identifier to all .gitignore files.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
powerpc/pseries: Move mm/book3s64/vphn.c under platforms/pseries/hcall_vphn() is specific to pseries and will be used in a subsequentpatch. So, move it to a more appropriate place underarch/power
powerpc/pseries: Move mm/book3s64/vphn.c under platforms/pseries/hcall_vphn() is specific to pseries and will be used in a subsequentpatch. So, move it to a more appropriate place underarch/powerpc/platforms/pseries. Also merge vphn.h into lppaca.hand update vphn selftest to use the new files.Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project
treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner <tglx@linutronix.de>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
powerpc/mm: Move book3s64 specifics in subdirectory mm/book3s64Many files in arch/powerpc/mm are only for book3S64. This patchcreates a subdirectory for them.Signed-off-by: Christophe Leroy <chr
powerpc/mm: Move book3s64 specifics in subdirectory mm/book3s64Many files in arch/powerpc/mm are only for book3S64. This patchcreates a subdirectory for them.Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>[mpe: Update the selftest sym links, shorten new filenames, cleanup some whitespace and formatting in the new files.]Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
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 thesel
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 <mpe@ellerman.id.au>
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
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 <kstewart@linuxfoundation.org>Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>Reviewed-by: Thomas Gleixner <tglx@linutronix.de>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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
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 <bamvor.zhangjian@linaro.org>Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
selftests/powerpc: Add install support to more powerpc testsThese tests were merged in parallel to the install support, update themnow to use it.This also adds cross compile support for the VPHN
selftests/powerpc: Add install support to more powerpc testsThese tests were merged in parallel to the install support, update themnow to use it.This also adds cross compile support for the VPHN test which was missingit.Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
selftests/powerpc: Add test for VPHNThe goal is to verify vphn_unpack_associativity() parses VPHN numberscorrectly. We feed it with a variety of input values and compare withexpected results.PA
selftests/powerpc: Add test for VPHNThe goal is to verify vphn_unpack_associativity() parses VPHN numberscorrectly. We feed it with a variety of input values and compare withexpected results.PAPR+ does not say much about VPHN parsing: I came up with a list oftests that check many simple cases and some corner ones. I wouldn'tdare to say the list is exhaustive though.Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>[mpe: Rework harness logic, rename to test-vphn, add -m64]Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>Reviewed-by: Greg Kurz <gkurz@linux.vnet.ibm.com>