From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Tom Zanussi <zanussi@kernel.org>,
axelrasmussen@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] tracing: Update synth command errors
Date: Wed, 9 Dec 2020 09:42:41 -0500 [thread overview]
Message-ID: <20201209094241.358e99ae@gandalf.local.home> (raw)
In-Reply-To: <20201209225114.9bb1f53caa5bc101a6e31a4b@kernel.org>
On Wed, 9 Dec 2020 22:51:14 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> This makes sense. Anyway, what I considered were
> - synthetic_events interface doesn't provide syntax error reports
> - synthetic_events interface is not self-reproducive*.
>
> *) I meant
>
> $ cat synthetic_events > saved_events
> $ cat saved_events > synthetic_events
>
> should work. But this does *NOT* mean
>
> $ cat user-input > synthetic_events
> $ cat synthetic_events > saved_events
> $ diff user-input saved_events # no diff
>
> So input and output can be different, but the output can be input again.
Totally agree.
Thanks,
-- Steve
next prev parent reply other threads:[~2020-12-09 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 15:06 [PATCH v3 0/5] tracing: More synthetic event error fixes Tom Zanussi
2020-10-26 15:06 ` [PATCH v3 1/5] tracing/dynevent: Delegate parsing to create function Tom Zanussi
2020-12-07 23:33 ` Steven Rostedt
2020-12-08 9:50 ` Masami Hiramatsu
2020-10-26 15:06 ` [PATCH v3 2/5] tracing: Rework synthetic event command parsing Tom Zanussi
2020-12-08 0:16 ` Steven Rostedt
2020-12-08 17:37 ` Tom Zanussi
2020-10-26 15:06 ` [PATCH v3 3/5] tracing: Update synth command errors Tom Zanussi
2020-12-08 1:13 ` Steven Rostedt
2020-12-08 17:34 ` Tom Zanussi
2020-12-08 17:53 ` Steven Rostedt
2020-12-08 18:32 ` Tom Zanussi
2020-12-09 13:51 ` Masami Hiramatsu
2020-12-09 14:42 ` Steven Rostedt [this message]
2020-10-26 15:06 ` [PATCH v3 4/5] selftests/ftrace: Add synthetic event field separators Tom Zanussi
2020-10-26 15:06 ` [PATCH v3 5/5] selftests/ftrace: Update synthetic event syntax errors Tom Zanussi
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=20201209094241.358e99ae@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=zanussi@kernel.org \
/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).