From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH 1/3] tracing: Combine enum and arrays into single macro in filter code
Date: Mon, 12 Mar 2018 19:31:24 +0900 [thread overview]
Message-ID: <20180312193124.7d295423e38317fb056e6ccd@kernel.org> (raw)
In-Reply-To: <20180310023907.528923886@goodmis.org>
On Fri, 09 Mar 2018 21:34:43 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
>
> Instead of having a separate enum that is the index into another array, like
> a string array, make a single macro that combines them into a single list,
> and then the two can not get out of sync. This makes it easier to add and
> remove items.
>
> The macro trick is:
>
> #define DOGS \
> C( JACK, "Jack Russell") \
> C( ITALIAN, "Italian Greyhound") \
> C( GERMAN, "German Shepherd")
>
> #undef C
> #define C(a, b) a
>
> enum { DOGS };
>
> #undef C
> #define C(a, b) b
>
> static char dogs[] = { DOGS };
Looks good to me, and nice idea :)
Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks,
>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> kernel/trace/trace_events_filter.c | 112 ++++++++++++++++---------------------
> 1 file changed, 48 insertions(+), 64 deletions(-)
>
> diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
> index c3c6eee1e4df..a2ef393b3bb2 100644
> --- a/kernel/trace/trace_events_filter.c
> +++ b/kernel/trace/trace_events_filter.c
> @@ -33,22 +33,26 @@
> "# Only events with the given fields will be affected.\n" \
> "# If no events are modified, an error message will be displayed here"
>
> -enum filter_op_ids
> -{
> - OP_OR,
> - OP_AND,
> - OP_GLOB,
> - OP_NE,
> - OP_EQ,
> - OP_LT,
> - OP_LE,
> - OP_GT,
> - OP_GE,
> - OP_BAND,
> - OP_NOT,
> - OP_NONE,
> - OP_OPEN_PAREN,
> -};
> +#define OPS \
> + C( OP_OR, "||", 1 ), \
> + C( OP_AND, "&&", 2 ), \
> + C( OP_GLOB, "~", 4 ), \
> + C( OP_NE, "!=", 4 ), \
> + C( OP_EQ, "==", 4 ), \
> + C( OP_LT, "<", 5 ), \
> + C( OP_LE, "<=", 5 ), \
> + C( OP_GT, ">", 5 ), \
> + C( OP_GE, ">=", 5 ), \
> + C( OP_BAND, "&", 6 ), \
> + C( OP_NOT, "!", 6 ), \
> + C( OP_NONE, "OP_NONE", 0 ), \
> + C( OP_OPEN_PAREN, "(", 0 ), \
> + C( OP_MAX, NULL, 0 )
> +
> +#undef C
> +#define C(a, b, c) a
> +
> +enum filter_op_ids { OPS };
>
> struct filter_op {
> int id;
> @@ -56,56 +60,36 @@ struct filter_op {
> int precedence;
> };
>
> -/* Order must be the same as enum filter_op_ids above */
> -static struct filter_op filter_ops[] = {
> - { OP_OR, "||", 1 },
> - { OP_AND, "&&", 2 },
> - { OP_GLOB, "~", 4 },
> - { OP_NE, "!=", 4 },
> - { OP_EQ, "==", 4 },
> - { OP_LT, "<", 5 },
> - { OP_LE, "<=", 5 },
> - { OP_GT, ">", 5 },
> - { OP_GE, ">=", 5 },
> - { OP_BAND, "&", 6 },
> - { OP_NOT, "!", 6 },
> - { OP_NONE, "OP_NONE", 0 },
> - { OP_OPEN_PAREN, "(", 0 },
> -};
> +#undef C
> +#define C(a, b, c) { a, b, c }
>
> -enum {
> - FILT_ERR_NONE,
> - FILT_ERR_INVALID_OP,
> - FILT_ERR_UNBALANCED_PAREN,
> - FILT_ERR_TOO_MANY_OPERANDS,
> - FILT_ERR_OPERAND_TOO_LONG,
> - FILT_ERR_FIELD_NOT_FOUND,
> - FILT_ERR_ILLEGAL_FIELD_OP,
> - FILT_ERR_ILLEGAL_INTVAL,
> - FILT_ERR_BAD_SUBSYS_FILTER,
> - FILT_ERR_TOO_MANY_PREDS,
> - FILT_ERR_MISSING_FIELD,
> - FILT_ERR_INVALID_FILTER,
> - FILT_ERR_IP_FIELD_ONLY,
> - FILT_ERR_ILLEGAL_NOT_OP,
> -};
> +static struct filter_op filter_ops[] = { OPS };
>
> -static char *err_text[] = {
> - "No error",
> - "Invalid operator",
> - "Unbalanced parens",
> - "Too many operands",
> - "Operand too long",
> - "Field not found",
> - "Illegal operation for field type",
> - "Illegal integer value",
> - "Couldn't find or set field in one of a subsystem's events",
> - "Too many terms in predicate expression",
> - "Missing field name and/or value",
> - "Meaningless filter expression",
> - "Only 'ip' field is supported for function trace",
> - "Illegal use of '!'",
> -};
> +#define ERRORS \
> + C( NONE, "No error"), \
> + C( INVALID_OP, "Invalid operator"), \
> + C( UNBALANCED_PAREN, "Unbalanced parens"), \
> + C( TOO_MANY_OPERANDS, "Too many operands"), \
> + C( OPERAND_TOO_LONG, "Operand too long"), \
> + C( FIELD_NOT_FOUND, "Field not found"), \
> + C( ILLEGAL_FIELD_OP, "Illegal operation for field type"), \
> + C( ILLEGAL_INTVAL, "Illegal integer value"), \
> + C( BAD_SUBSYS_FILTER, "Couldn't find or set field in one of a subsystem's events"), \
> + C( TOO_MANY_PREDS, "Too many terms in predicate expression"), \
> + C( MISSING_FIELD, "Missing field name and/or value"), \
> + C( INVALID_FILTER, "Meaningless filter expression"), \
> + C( IP_FIELD_ONLY, "Only 'ip' field is supported for function trace"), \
> + C( ILLEGAL_NOT_OP, "Illegal use of '!'"),
> +
> +#undef C
> +#define C(a, b) FILT_ERR_##a
> +
> +enum { ERRORS };
> +
> +#undef C
> +#define C(a, b) b
> +
> +static char *err_text[] = { ERRORS };
>
> struct opstack_op {
> enum filter_op_ids op;
> --
> 2.15.1
>
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2018-03-12 10:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 2:34 [PATCH 0/3] tracing: Rewrite the function " Steven Rostedt
2018-03-10 2:34 ` [PATCH 1/3] tracing: Combine enum and arrays into single macro in " Steven Rostedt
2018-03-12 10:31 ` Masami Hiramatsu [this message]
2018-03-10 2:34 ` [PATCH 2/3] tracing: Clean up and document pred_funcs_##type creation and use Steven Rostedt
2018-03-12 13:42 ` Masami Hiramatsu
2018-03-10 2:34 ` [PATCH 3/3] tracing: Rewrite filter logic to be simpler and faster Steven Rostedt
2018-03-10 3:10 ` Steven Rostedt
2018-03-10 3:15 ` Steven Rostedt
2018-03-10 3:22 ` Steven Rostedt
2018-03-10 3:18 ` Steven Rostedt
2018-03-12 12:42 ` Jiri Olsa
2018-03-12 18:38 ` Steven Rostedt
2018-03-12 15:10 ` Jiri Olsa
2018-03-12 18:40 ` Steven Rostedt
2018-03-12 18:54 ` Jiri Olsa
2018-03-12 19:10 ` Steven Rostedt
2018-03-12 23:52 ` Steven Rostedt
2018-03-13 10:14 ` Jiri Olsa
2018-03-13 14:12 ` Steven Rostedt
2018-03-13 14:27 ` Jiri Olsa
2018-03-11 19:54 ` [PATCH 0/3] tracing: Rewrite the function filter code Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2018-03-09 20:05 [PATCH v3] kernel.h: Skip single-eval logic on literals in min()/max() Kees Cook
2018-03-09 21:10 ` Linus Torvalds
2018-03-09 21:47 ` Kees Cook
2018-03-11 22:46 ` Tobin C. Harding
2018-03-13 13:31 ` David Laight
2018-03-10 0:07 ` Andrew Morton
2018-03-10 0:28 ` Linus Torvalds
2018-03-10 0:32 ` Andrew Morton
2018-03-10 0:38 ` Linus Torvalds
2018-03-10 1:30 ` Kees Cook
2018-03-10 1:31 ` Kees Cook
2018-03-10 2:37 ` Linus Torvalds
2018-03-12 22:55 ` Andrew Morton
2018-03-12 23:57 ` Linus Torvalds
2018-03-13 4:28 ` Kees Cook
2018-03-13 21:02 ` Andrew Morton
2018-03-13 22:14 ` Kees Cook
2018-03-14 11:35 ` David Laight
2018-03-10 3:11 ` Randy Dunlap
2018-03-10 6:10 ` Miguel Ojeda
2018-03-10 7:03 ` Miguel Ojeda
2018-03-10 16:04 ` Linus Torvalds
2018-03-10 15:33 ` Kees Cook
2018-03-10 16:11 ` Linus Torvalds
2018-03-10 16:30 ` Linus Torvalds
2018-03-10 17:34 ` Miguel Ojeda
2018-03-10 17:51 ` Linus Torvalds
2018-03-10 19:08 ` Miguel Ojeda
2018-03-11 11:05 ` Ingo Molnar
2018-03-11 18:23 ` Linus Torvalds
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=20180312193124.7d295423e38317fb056e6ccd@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.com \
--cc=viro@ZenIV.linux.org.uk \
/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
Powered by JetHome