tracing: Fix config dependency and trigger parser
Get series with b4
b4 am 159262474473.185015.177609153974879988.stgit@devnote2Versions newest first
- v1 Latest2 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | tracing/boot: Fix config dependency for synthedic eventkernel/ | +1 | 0 replies | |
| 2/2 | tracing: Fix event trigger to accept redundant spaceskernel/ | +19 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Tom Zanussi |
|---|---|
| Series | R-b |
| 1/2 | |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] tracing: Fix config dependency and trigger parser
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) <[email protected]>