Commit 82f4f3e6 authored Jul 14, 2018 by Masami Hiramatsu Committed by Steven Rostedt (VMware) Jul 25, 2018

selftests/ftrace: Add snapshot and tracing_on test case

Add a testcase for checking snapshot and tracing_on
relationship. This ensures that the snapshotting doesn't
affect current tracing on/off settings.

Link: http://lkml.kernel.org/r/153149932412.11274.15289227592627901488.stgit@devbox



Cc: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: Hiraku Toyooka <hiraku.toyooka@cybertrust.co.jp>
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

parent 73c8d894

tools/testing/selftests/ftrace/test.d/00basic/snapshot.tc

0 → 100644

+28 −0

Original line number	Diff line number	Diff line
		#!/bin/sh
		# description: Snapshot and tracing setting
		# flags: instance

		[ ! -f snapshot ] && exit_unsupported

		echo "Set tracing off"
		echo 0 > tracing_on

		echo "Allocate and take a snapshot"
		echo 1 > snapshot

		# Since trace buffer is empty, snapshot is also empty, but allocated
		grep -q "Snapshot is allocated" snapshot

		echo "Ensure keep tracing off"
		test `cat tracing_on` -eq 0

		echo "Set tracing on"
		echo 1 > tracing_on

		echo "Take a snapshot again"
		echo 1 > snapshot

		echo "Ensure keep tracing on"
		test `cat tracing_on` -eq 1

		exit 0