From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH 0/3] tracing/filters: new event parser
Date: Tue, 28 Apr 2009 11:50:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0904281149280.8066@gandalf.stny.rr.com> (raw)
In-Reply-To: <1240905879.6416.118.camel@tropicana>
On Tue, 28 Apr 2009, Tom Zanussi wrote:
> This patchset replaces the current event parser hack with a better, more
> extensible version. See patch 3 for the details on syntax and usage.
>
> Basically, instead of defining a filter predicate by predicate as in the
> current version, you now define the whole thing all at once and in
> addition to the current == and != operators, can use >, <, >=, <=,
> parens and the logical operators && and ||. Some examples:
>
> # echo "((sig >= 10 && sig < 15) || sig == 17) && comm != bash" > filter
>
> # echo "common_preempt_count > 4" > filter
>
> # echo "common_preempt_count > 4 && common_pid != 0" > filter
>
> It also does some basic error reporting, which you can see by cat'ing
> the filter file after a failed set (this needs a little more work to
> report the error position, but is still useful):
>
> # echo "(sig >= 10 && sig < 15) || dsig == 17) && comm != bash" > filter
> -bash: echo: write error: Invalid argument
> # cat filter
> (sig >= 10 && sig < 15) || dsig == 17) && comm != bash
> ^
> parse_error: Unbalanced parens
>
> It should be relatively easy to add new operators; it's implemented as a
> standard infix to postfix converter - when a filter is defined, as
> before, it creates a set of predicates that are evaluated efficiently at
> run-time.
>
> I tried to make the parser itself reusable so that it could also be
> pointed at a completely separate set of operators and an unevaluated
> operand, with the resulting expression components available in the
> intermediate postfix list. e.g. for say a field of type dev_t, the
> parser could be set up and pointed at an operand of the form (8,3) or
> 8:3 or /dev/sda, and the parsed results retrieved from the parse state
> object, something like this:
>
> enum kdev_t_filter_op_ids
> {
> COMMA_OP,
> };
>
> struct filter_op kdev_t_filter_ops[] = {
> { COMMA_OP, ",", 1 },
> { NO_OP, "NO_OP", 0 },
> { OPEN_PAREN_OP, "(", 0 },
> };
>
> parse_init(parse_state, kdev_t_filter_ops, dev_string);
> filter_parse(parse_state);
>
> The parsed operator and operands could then be found in the
> parse_state.postfix list and used to generate the dev_t value, or if it
> was specified as a string ('sda' or /dev/sda), there would only be one
> item in the list which could be used in that case to look up the value.
>
Hi Tom,
Cool stuff. I just skimmed the patches and did not see anything
I object to.
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
prev parent reply other threads:[~2009-04-28 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 8:04 Tom Zanussi
2009-04-28 11:22 ` Ingo Molnar
2009-04-28 15:50 ` 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=alpine.DEB.2.00.0904281149280.8066@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=tzanussi@gmail.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
all inboxes | Powered by JetHome®