aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/intel_pstate
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2018-03-23 20:44:27 +1100
committerShuah Khan <shuahkh@osg.samsung.com>2018-03-26 14:54:19 -0600
commit88893cf787d3062c631cc20b875068eb11756e03 (patch)
tree8a509e0583d314365a0598034721ec562b868ef0 /tools/testing/selftests/intel_pstate
parentselftests/seccomp: Allow get_metadata to XFAIL (diff)
downloadlinux-dev-88893cf787d3062c631cc20b875068eb11756e03.tar.xz
linux-dev-88893cf787d3062c631cc20b875068eb11756e03.zip
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/testing/selftests/intel_pstate')
0 files changed, 0 insertions, 0 deletions