From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Tom Zanussi <zanussi@kernel.org>
Subject: [PATCH 0/2] tracing: Fix config dependency and trigger parser
Date: Sat, 20 Jun 2020 12:45:44 +0900 [thread overview]
Message-ID: <159262474473.185015.177609153974879988.stgit@devnote2> (raw)
Hi,
These are some fixes which I found recentry on ftrace.
- Since the boot-time tracing synthetic event feature is decoupled
from trigger recenty, it should use CONFIG_SYNTH_EVENT.
- The parser of event trigger seems rejecting some redundant
spaces. But it is hard users to find the wrong point. Such
spaces should be accepted.
BTW, I also found the trigger parser accepts some inputs which
may not correctly formatted, e.g.
# echo "traceon 1" > events/ftrace/print/trigger
(from the document, it must be "traceon:1")
But I think this does not decrease the usability.
Thank you,
---
Masami Hiramatsu (2):
tracing/boot: Fix config dependency for synthedic event
tracing: Fix event trigger to accept redundant spaces
kernel/trace/trace_boot.c | 2 +-
kernel/trace/trace_events_trigger.c | 21 +++++++++++++++++++--
2 files changed, 20 insertions(+), 3 deletions(-)
--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next reply other threads:[~2020-06-20 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 3:45 Masami Hiramatsu [this message]
2020-06-20 3:45 ` [PATCH 1/2] tracing/boot: Fix config dependency for synthedic event Masami Hiramatsu
2020-06-20 3:46 ` [PATCH 2/2] tracing: Fix event trigger to accept redundant spaces Masami Hiramatsu
2020-06-23 21:03 ` [PATCH 0/2] tracing: Fix config dependency and trigger parser 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=159262474473.185015.177609153974879988.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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