linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	linux-api@vger.kernel.org, Shuah Khan <shuahkh@osg.samsung.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] kselftests/ftrace : Add event trigger testcases
Date: Thu, 15 Oct 2015 20:27:01 -0400	[thread overview]
Message-ID: <20151015202701.752af971@grimm.local.home> (raw)
In-Reply-To: <55BD4AC5.8040905@hitachi.com>

On Sun, 02 Aug 2015 07:40:05 +0900
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:

> On 2015/07/27 18:34, Namhyung Kim wrote:
> > Hi Masami,
> > 
> > On Sat, Jul 25, 2015 at 10:13:10AM +0900, Masami Hiramatsu wrote:
> >> This adds simple event trigger testcases for ftracetest,
> >> which covers following triggers.
> >>  - traceon-traceoff trigger
> >>  - enable/disable_event trigger
> >>  - snapshot trigger
> >>  - stacktrace trigger
> >>  - trigger filters
> >>
> >> Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> >> Cc: Steven Rostedt <rostedt@goodmis.org>
> >> Cc: Ingo Molnar <mingo@redhat.com>
> >> Cc: Shuah Khan <shuahkh@osg.samsung.com>
> >> Cc: Namhyung Kim <namhyung@kernel.org>
> >> Cc: Tom Zanussi <tom.zanussi@linux.intel.com>
> >> ---
> >>  tools/testing/selftests/ftrace/test.d/functions    |    9 +++
> >>  .../ftrace/test.d/trigger/trigger-eventonoff.tc    |   64 ++++++++++++++++++++
> >>  .../ftrace/test.d/trigger/trigger-filter.tc        |   59 ++++++++++++++++++
> >>  .../ftrace/test.d/trigger/trigger-snapshot.tc      |   56 ++++++++++++++++++
> >>  .../ftrace/test.d/trigger/trigger-stacktrace.tc    |   53 +++++++++++++++++
> >>  .../ftrace/test.d/trigger/trigger-traceonoff.tc    |   58 ++++++++++++++++++
> >>  6 files changed, 299 insertions(+)
> >>  create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-eventonoff.tc
> >>  create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-filter.tc
> >>  create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-snapshot.tc
> >>  create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-stacktrace.tc
> >>  create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-traceonoff.tc
> >>
> >> diff --git a/tools/testing/selftests/ftrace/test.d/functions b/tools/testing/selftests/ftrace/test.d/functions
> >> index 5d8cd06..36ca18e 100644
> >> --- a/tools/testing/selftests/ftrace/test.d/functions
> >> +++ b/tools/testing/selftests/ftrace/test.d/functions
> >> @@ -14,3 +14,12 @@ enable_tracing() { # start trace recording
> >>  reset_tracer() { # reset the current tracer
> >>      echo nop > current_tracer
> >>  }
> >> +
> >> +reset_trigger() { # reset all current setting triggers
> >> +    grep -v ^# events/*/*/trigger |
> >> +    while read line; do
> >> +        cmd=`echo $line | cut -f2- -d:`
> >> +	echo "!$cmd" > `echo $line | cut -f1 -d:`
> > 
> > Broken whitespaces?
> 
> Right, I'll fix that.
> 

[..]

> > What about checking child_comm too to verify complex filter pattern
> > with string type?  Maybe something like below (not tested..)?
> > 
> > echo 'traceoff if child_pid != 0 && child_comm ~ '*sh' > events/.../trigger
> 
> OK, I'll add more complex patterns.

Hi Masami,

Did you ever send an updated patch?

-- Steve

      reply	other threads:[~2015-10-16  0:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25  1:13 [PATCH] kselftests/ftrace : Add event trigger testcases Masami Hiramatsu
     [not found] ` <20150725011310.4601.76087.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-07-27  9:34   ` Namhyung Kim
2015-08-01 22:40     ` Masami Hiramatsu
2015-10-16  0:27       ` Steven Rostedt [this message]

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=20151015202701.752af971@grimm.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=tom.zanussi@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).