From: Shuah Khan <shuahkh@osg.samsung.com>
To: Namhyung Kim <namhyung@kernel.org>, Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 2/2] kselftests/ftrace: Add a test case for event pid filtering
Date: Tue, 10 May 2016 09:24:40 -0600 [thread overview]
Message-ID: <5731FD38.3080203@osg.samsung.com> (raw)
In-Reply-To: <1462891986-3608-2-git-send-email-namhyung@kernel.org>
On 05/10/2016 08:53 AM, Namhyung Kim wrote:
> Check event is filtered by set_event_pid and options/event-fork.
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Looks good to me. Steve! Ack if you are good with this patch.
I can get this into 4.8-rc1
thanks,
-- Shuah
> ---
> .../selftests/ftrace/test.d/event/event-pid.tc | 72 ++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 tools/testing/selftests/ftrace/test.d/event/event-pid.tc
>
> diff --git a/tools/testing/selftests/ftrace/test.d/event/event-pid.tc b/tools/testing/selftests/ftrace/test.d/event/event-pid.tc
> new file mode 100644
> index 000000000000..d4ab27b522f8
> --- /dev/null
> +++ b/tools/testing/selftests/ftrace/test.d/event/event-pid.tc
> @@ -0,0 +1,72 @@
> +#!/bin/sh
> +# description: event tracing - restricts events based on pid
> +
> +do_reset() {
> + echo > set_event
> + echo > set_event_pid
> + echo 0 > options/event-fork
> + clear_trace
> +}
> +
> +fail() { #msg
> + do_reset
> + echo $1
> + exit $FAIL
> +}
> +
> +yield() {
> + ping localhost -c 1 || sleep .001 || usleep 1 || sleep 1
> +}
> +
> +if [ ! -f set_event -o ! -d events/sched ]; then
> + echo "event tracing is not supported"
> + exit_unsupported
> +fi
> +
> +if [ ! -f set_event_pid ]; then
> + echo "event pid filtering is not supported"
> + exit_unsupported
> +fi
> +
> +reset_tracer
> +do_reset
> +
> +echo 1 > events/sched/sched_switch/enable
> +
> +yield
> +
> +count=`cat trace | grep sched_switch | wc -l`
> +if [ $count -eq 0 ]; then
> + fail "sched_switch events are not recorded"
> +fi
> +
> +do_reset
> +
> +read mypid rest < /proc/self/stat
> +
> +echo $mypid > set_event_pid
> +echo 'sched:sched_switch' > set_event
> +
> +yield
> +
> +count=`cat trace | grep sched_switch | grep -v "pid=$mypid" | wc -l`
> +if [ $count -ne 0 ]; then
> + fail "sched_switch events from other task are recorded"
> +fi
> +
> +do_reset
> +
> +echo $mypid > set_event_pid
> +echo 1 > options/event-fork
> +echo 1 > events/sched/sched_switch/enable
> +
> +yield
> +
> +count=`cat trace | grep sched_switch | grep -v "pid=$mypid" | wc -l`
> +if [ $count -eq 0 ]; then
> + fail "sched_switch events from other task are not recorded"
> +fi
> +
> +do_reset
> +
> +exit 0
>
next prev parent reply other threads:[~2016-05-10 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 14:53 [PATCH 1/2] kselftests/ftrace: Detect tracefs mount point Namhyung Kim
2016-05-10 14:53 ` [PATCH 2/2] kselftests/ftrace: Add a test case for event pid filtering Namhyung Kim
2016-05-10 15:24 ` Shuah Khan [this message]
2016-05-16 16:12 ` Shuah Khan
2016-05-10 15:24 ` [PATCH 1/2] kselftests/ftrace: Detect tracefs mount point Shuah Khan
2016-05-16 16:12 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5731FD38.3080203@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox