selftests/drivers/gpu: Add error messages to drm_mm.shAdd error messages when the module test-drm_mm is not found or couldnot be removed to make tests output more readable.Signed-off-by: Gautam
selftests/drivers/gpu: Add error messages to drm_mm.shAdd error messages when the module test-drm_mm is not found or couldnot be removed to make tests output more readable.Signed-off-by: Gautam Menghani <gautammenghani201@gmail.com>Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
show more ...
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>
drm/i915: Provide a hook for selftestsSome pieces of code are independent of hardware but are very tricky toexercise through the normal userspace ABI or via debugfs hooks. Beingable to create moc
drm/i915: Provide a hook for selftestsSome pieces of code are independent of hardware but are very tricky toexercise through the normal userspace ABI or via debugfs hooks. Beingable to create mock unit tests and execute them through CI is vital.Start by adding a central point where we can execute unit tests anda parameter to enable them. This is disabled by default as theexpectation is that these tests will occasionally explode.To facilitate integration with igt, any parameter beginning withi915.igt__ is interpreted as a subtest executable independently viaigt/drv_selftest.Two classes of selftests are recognised: mock unit tests and integrationtests. Mock unit tests are run as soon as the module is loaded, beforethe device is probed. At that point there is no driver instantiated andall hw interactions must be "mocked". This is very useful for writinguniversal tests to exercise code not typically run on a broad range ofarchitectures. Alternatively, you can hook into the live selftests andrun when the device has been instantiated - hw interactions are real.v2: Add a macro for compiling conditional code for mock objects insidereal objects.v3: Differentiate between mock unit tests and late integration test.v4: List the tests in natural order, use igt to sort after modparam.v5: s/late/live/v6: s/unsigned long/unsigned int/v7: Use igt_ prefixes for long helpers.v8: Deobfuscate macros overriding functions, stop using -I$(src)Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>Link: http://patchwork.freedesktop.org/patch/msgid/20170213171558.20942-1-chris@chris-wilson.co.uk
Merge tag 'drm-misc-next-2016-12-30' of git://anongit.freedesktop.org/git/drm-misc into drm-intel-next-queuedDirectly merge drm-misc into drm-intel since Dave is on vacation andwe need the various
Merge tag 'drm-misc-next-2016-12-30' of git://anongit.freedesktop.org/git/drm-misc into drm-intel-next-queuedDirectly merge drm-misc into drm-intel since Dave is on vacation andwe need the various drm-misc patches (fb format rework, drm mm fixes,selftest framework and others). Also pulled back -rc2 in first toresync with drm-intel-fixes and make sure I can reuse the exact rereresolutions from drm-tip for safety, and because I'm lazy.Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
drm: Add some kselftests for the DRM range manager (struct drm_mm)First we introduce a smattering of infrastructure for writing selftests.The idea is that we have a test module that exercises a pa
drm: Add some kselftests for the DRM range manager (struct drm_mm)First we introduce a smattering of infrastructure for writing selftests.The idea is that we have a test module that exercises a particularportion of the exported API, and that module provides a set of teststhat can either be run as an ensemble via kselftest or individually viaan igt harness (in this case igt/drm_mm). To accommodate selectingindividual tests, we export a boolean parameter to control selection ofeach test - that is hidden inside a bunch of reusable boilerplate macrosto keep writing the tests simple.v2: Choose a random random_seed unless one is specified by the user.v3: More parameters to control max_iterations and max_prime of thetests.Testcase: igt/drm_mmSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>Acked-by: Christian König <christian.koenig@amd.com>Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>Link: http://patchwork.freedesktop.org/patch/msgid/20161222083641.2691-7-chris@chris-wilson.co.uk
kselftests: Exercise hw-independent mock tests for i915.koAlthough being a GPU driver most functionality of i915.ko depends uponreal hardware, many of its internal interfaces can be "mocked" and s
kselftests: Exercise hw-independent mock tests for i915.koAlthough being a GPU driver most functionality of i915.ko depends uponreal hardware, many of its internal interfaces can be "mocked" and sotested independently of any hardware. Expanding the test coverage is notonly useful for i915.ko, but should provide some integration tests forcore infrastructure as well.Loading i915.ko with mock_selftests=-1 will cause it to execute its mocktests then fail with -ENOTTY. If the driver is already loaded and boundto hardware, it requires a few more steps to unbind, and so the simplepreliminary modprobe -r will fail.Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>Cc: Shuah Khan <shuah@kernel.org>Cc: linux-kselftest@vger.kernel.orgSigned-off-by: Shuah Khan <shuahkh@osg.samsung.com>