summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/proc/Makefile
diff options
context:
space:
mode:
authorAlexey Dobriyan <adobriyan@gmail.com>2018-04-11 02:43:28 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2018-04-11 20:28:34 +0300
commit1f5bd0547654ada423b184e22f320d76c0fac49e (patch)
tree0d305b2d1f713af5bf4b9b534cb253183a58e716 /tools/testing/selftests/proc/Makefile
parent4f1134370a29a5f2d0f4b4be4c5e2fddd38f0f9d (diff)
downloadlinux-1f5bd0547654ada423b184e22f320d76c0fac49e.tar.xz
proc: selftests: test /proc/uptime
The only tests I could come up with for /proc/uptime are: - test that values increase monotonically for 1 second, - bounce around CPUs and test the same thing. Avoid glibc like plague for affinity given patches like this: https://marc.info/?l=linux-kernel&m=152130031912594&w=4 Link: http://lkml.kernel.org/r/20180317165235.GB3445@avx2 Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com> Cc: Shuah Khan <shuah@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/testing/selftests/proc/Makefile')
-rw-r--r--tools/testing/selftests/proc/Makefile2
1 files changed, 2 insertions, 0 deletions
diff --git a/tools/testing/selftests/proc/Makefile b/tools/testing/selftests/proc/Makefile
index 312a3989820c..dbb87e56264c 100644
--- a/tools/testing/selftests/proc/Makefile
+++ b/tools/testing/selftests/proc/Makefile
@@ -6,6 +6,8 @@ TEST_GEN_PROGS += proc-self-map-files-001
TEST_GEN_PROGS += proc-self-map-files-002
TEST_GEN_PROGS += proc-self-syscall
TEST_GEN_PROGS += proc-self-wchan
+TEST_GEN_PROGS += proc-uptime-001
+TEST_GEN_PROGS += proc-uptime-002
TEST_GEN_PROGS += read
include ../lib.mk