selftests: Print the test we're running to /dev/kmsg
authorMichael Ellerman <mpe@ellerman.id.au>
Fri, 23 Mar 2018 09:44:27 +0000 (20:44 +1100)
committerShuah Khan <shuahkh@osg.samsung.com>
Mon, 26 Mar 2018 20:54:19 +0000 (14:54 -0600)
commit88893cf787d3062c631cc20b875068eb11756e03
tree8a509e0583d314365a0598034721ec562b868ef0
parent6c3b6d50839151c5d8a077610b5d8c3dc1e7e7b3
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>
tools/testing/selftests/Makefile