diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2018-03-23 20:44:27 +1100 |
|---|---|---|
| committer | Shuah Khan <shuahkh@osg.samsung.com> | 2018-03-26 14:54:19 -0600 |
| commit | 88893cf787d3062c631cc20b875068eb11756e03 (patch) | |
| tree | 8a509e0583d314365a0598034721ec562b868ef0 /tools | |
| parent | 6c3b6d50839151c5d8a077610b5d8c3dc1e7e7b3 (diff) | |
| download | linux-88893cf787d3062c631cc20b875068eb11756e03.tar.bz2 | |
selftests: Print the test we're running to /dev/kmsg
Some tests cause the kernel to print things to the kernel log
buffer (ie. printk), in particular oops and warnings etc. However when
running all the tests in succession it's not always obvious which
test(s) caused the kernel to print something.
We can narrow it down by printing which test directory we're running
in to /dev/kmsg, if it's writable.
Example output:
[ 170.149149] kselftest: Running tests in powerpc
[ 305.300132] kworker/dying (71) used greatest stack depth: 7776 bytes
left
[ 808.915456] kselftest: Running tests in pstore
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/testing/selftests/Makefile | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile index a41b4be28b9f..f4dfee6ea8a4 100644 --- a/tools/testing/selftests/Makefile +++ b/tools/testing/selftests/Makefile @@ -138,6 +138,7 @@ ifdef INSTALL_PATH echo "echo ; echo TAP version 13" >> $(ALL_SCRIPT); \ echo "echo Running tests in $$TARGET" >> $(ALL_SCRIPT); \ echo "echo ========================================" >> $(ALL_SCRIPT); \ + echo "[ -w /dev/kmsg ] && echo \"kselftest: Running tests in $$TARGET\" >> /dev/kmsg" >> $(ALL_SCRIPT); \ echo "cd $$TARGET" >> $(ALL_SCRIPT); \ make -s --no-print-directory OUTPUT=$$BUILD_TARGET -C $$TARGET emit_tests >> $(ALL_SCRIPT); \ echo "cd \$$ROOT" >> $(ALL_SCRIPT); \ |