From: Masami Hiramatsu <mhiramat@kernel.org>
To: Tom Zanussi <zanussi@kernel.org>
Cc: rostedt@goodmis.org, mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] tracing: Improve error messages for histogram sorting
Date: Fri, 28 Jun 2019 15:16:45 +0900 [thread overview]
Message-ID: <20190628151645.a81b327d8e0d7c68d521b24e@kernel.org> (raw)
In-Reply-To: <cover.1561647046.git.zanussi@kernel.org>
On Thu, 27 Jun 2019 10:35:15 -0500
Tom Zanussi <zanussi@kernel.org> wrote:
> Hi,
>
> These patches add some improvements for histogram sorting, addressing
> some shortcomings pointed out by Masami.
>
> In order to address the specific problem pointed out by Masami, as
> well as add additional related error messages, the first patch
> does some simplification of assignment parsing.
>
> The second patch actually adds the new error messages.
>
> The fourth patch adds a new testcase for hist trigger parsing, similar
> to the same kind of tests for kprobes and uprobes. Additional tests
> covering all possible hist trigger errors should/will be added here in
> the future.
>
> The third patch just adds a missing hist: prefix to the error log so
> that the testcases work properly, and which should have been there
> anyway.
>
> Thanks,
Hi Tom,
These patches look good to me :)
Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
for all patches. BTW, if you think there is a bug and the 1st one fixes it,
please add Fixes: tag.
Thank you,
>
> Tom
>
> The following changes since commit a124692b698b00026a58d89831ceda2331b2e1d0:
>
> ftrace: Enable trampoline when rec count returns back to one (2019-05-25 23:04:43 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace-hist-sort-err-msgs-v1
>
> Tom Zanussi (4):
> tracing: Simplify assignment parsing for hist triggers
> tracing: Add hist trigger error messages for sort specification
> tracing: Add 'hist:' to hist trigger error log error string
> tracing: Add new testcases for hist trigger parsing errors
>
> kernel/trace/trace_events_hist.c | 94 +++++++++++-----------
> .../test.d/trigger/trigger-hist-syntax-errors.tc | 32 ++++++++
> 2 files changed, 78 insertions(+), 48 deletions(-)
> create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-syntax-errors.tc
>
> --
> 2.14.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2019-06-28 6:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 15:35 Tom Zanussi
2019-06-27 15:35 ` [PATCH 1/4] tracing: Simplify assignment parsing for hist triggers Tom Zanussi
2019-06-28 5:39 ` Masami Hiramatsu
2019-06-28 13:42 ` Tom Zanussi
2019-06-27 15:35 ` [PATCH 2/4] tracing: Add hist trigger error messages for sort specification Tom Zanussi
2019-06-27 15:35 ` [PATCH 3/4] tracing: Add 'hist:' to hist trigger error log error string Tom Zanussi
2019-06-27 15:35 ` [PATCH 4/4] tracing: Add new testcases for hist trigger parsing errors Tom Zanussi
2019-06-28 6:16 ` Masami Hiramatsu [this message]
2019-06-28 13:44 ` [PATCH 0/4] tracing: Improve error messages for histogram sorting 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=20190628151645.a81b327d8e0d7c68d521b24e@kernel.org \
--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
all inboxes | Powered by JetHome®