From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/5] ftrace: Support full glob matching
Date: Thu, 20 Oct 2016 11:07:52 +0900 [thread overview]
Message-ID: <20161020110752.460115c2a5dcbb719de29423@kernel.org> (raw)
In-Reply-To: <20161019092057.203b7b12@gandalf.local.home>
On Wed, 19 Oct 2016 09:20:57 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 19 Oct 2016 13:53:36 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Use glob_match() to support flexible glob wildcards (*,?)
> > and character classes ([) for ftrace.
> > Since the full glob matching is slower than the current
> > partial matching routines(*pat, pat*, *pat*), this leaves
> > those routines and just add MATCH_GLOB for complex glob
> > expression.
> >
> > e.g.
> > ----
> > [root@localhost tracing]# echo 'sched*group' > set_ftrace_filter
> > [root@localhost tracing]# cat set_ftrace_filter
> > sched_free_group
> > sched_change_group
> > sched_create_group
> > sched_online_group
> > sched_destroy_group
> > sched_offline_group
> > [root@localhost tracing]# echo '[Ss]y[Ss]_*' > set_ftrace_filter
> > [root@localhost tracing]# head set_ftrace_filter
> > sys_arch_prctl
> > sys_rt_sigreturn
> > sys_ioperm
> > SyS_iopl
> > sys_modify_ldt
> > SyS_mmap
> > SyS_set_thread_area
> > SyS_get_thread_area
> > SyS_set_tid_address
> > sys_fork
> > ----
>
> Hi Masami,
>
> Is this any different than your last patch, as I already pulled it into
> my queue. I haven't been able to test it much, as I found that 4.9-rc1
> is failing my tests, and I can't add new code to linux-next till 4.9 is
> stable.
This patch is completely same as the last patch. If you already queued it,
please ignore this [1/5].
And OK, what kind of tests are failed on 4.9-rc1? I though a possible
kernel freeze in 4.8 when I ran ftracetest, but it seemed disappeared
in 4.9-rc1.
Thanks,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2016-10-20 2:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 4:53 [PATCH 0/5] ftrace: selftests: Add full glob matching and update ftracetest Masami Hiramatsu
2016-10-19 4:53 ` [PATCH 1/5] ftrace: Support full glob matching Masami Hiramatsu
2016-10-19 13:20 ` Steven Rostedt
2016-10-20 2:07 ` Masami Hiramatsu [this message]
2016-10-20 13:43 ` Steven Rostedt
2016-10-21 16:43 ` Masami Hiramatsu
2016-10-19 4:53 ` [PATCH 2/5] selftests: ftrace: Fix test cases to enable tracing Masami Hiramatsu
2016-10-24 19:50 ` Steven Rostedt
2016-10-25 9:51 ` Masami Hiramatsu
2016-10-19 4:53 ` [PATCH 3/5] selftests: ftrace: Introduce TMPDIR for temporary files Masami Hiramatsu
2016-10-19 4:54 ` [PATCH 4/5] selftests: ftrace: Add a testcase for function filter glob match Masami Hiramatsu
2016-10-19 4:54 ` [PATCH 5/5] selftests: ftrace: Add a testcase for types of kprobe event Masami Hiramatsu
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=20161020110752.460115c2a5dcbb719de29423@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--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