Re: [PATCH v2 0/5] Add glob pattern matching support on trigger and kprobe-event
From: Steven Rostedt
Date: Wed Jun 18 2014 - 21:27:19 EST
A blast from the past! (I'm cleaning out my inbox).
On Wed, 22 May 2013 11:19:03 +0900
Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx> wrote:
> Hi,
>
> Here is a series of ftrace/perf updates to support multiple
> event select operation by glob-based wild cards.
>
> I've ported strglobmatch from perf-tools (with recursive call
> limitation) for this use. It is easier to use (just replacing
> strcmp) but slower than current parser-based matching.
> I don't care about the speed of matching because the all of
> the matching which I've introduced in this series are done
> on slow-path.
>
> Changes in v2:
> - Update the comment of patch [2/5] for explaining more
> detail of the backgroud.
>
> ---
>
> Masami Hiramatsu (5):
> [BUGFIX] tracing: Returns -EBUSY when event_enable_func fails to get module
This is applied.
> perf: Swap the parameters of strglobmatch
> lib/string: Add a generic wildcard string matching function
> tracing/kprobes: Allow user to delete kprobe events by wild cards
> tracing: Support enable/disable multiple events trigger by wild cards
These don't look to be applied. Looks like this patch series was lost.
Masami, are these still relevant?
-- Steve
>
>
> Documentation/trace/ftrace.txt | 12 ++-
> Documentation/trace/kprobetrace.txt | 19 +++--
> include/linux/string.h | 8 ++
> kernel/trace/trace_events.c | 121 +++++++++++++++++++++++++----------
> kernel/trace/trace_kprobe.c | 97 ++++++++++++++++++++--------
> lib/string.c | 91 ++++++++++++++++++++++++++
> tools/perf/util/parse-events.c | 14 ++--
> tools/perf/util/probe-event.c | 2 -
> tools/perf/util/strfilter.c | 2 -
> tools/perf/util/string.c | 16 ++---
> tools/perf/util/util.h | 4 +
> 11 files changed, 295 insertions(+), 91 deletions(-)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/