From: Tom Zanussi <zanussi@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: rostedt@goodmis.org, tglx@linutronix.de, namhyung@kernel.org,
bigeasy@linutronix.de, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/5] tracing: common error_log for ftrace
Date: Thu, 14 Feb 2019 09:15:23 -0600 [thread overview]
Message-ID: <1550157323.2498.2.camel@kernel.org> (raw)
In-Reply-To: <20190214121357.727a0f34246b51e6660354bc@kernel.org>
Hi Masami,
On Thu, 2019-02-14 at 12:13 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> Thank you for your great work!
Thanks!
>
> On Wed, 13 Feb 2019 12:17:51 -0600
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > From: Tom Zanussi <tom.zanussi@linux.intel.com>
> >
> > Last April, I posted an RFC patchset [1] implementing a common
> > error_log interface as suggested by Masami [2]. We were supposed
> > to
> > discuss it at Plumbers but that never happened, and Steve recently
> > asked about patches for a follow-on discussion [3], so here they
> > are.
> >
> >
[snip]
> > # cat /sys/kernel/debug/tracing/error_log
> > hist:sched:sched_wakeup: error: Variable already defined
> > Command: keys=pid:ts0=common_timestamp.usecs if
> > comm=="cyclictest"
> > ^
> > hist:sched:sched_waking: error: Couldn't find onmax or onchange
> > variable
> > Command: key=comm:p=prio:onchange($q).snapshot()
> > ^
> > hist:sched:sched_wakeup: error: Hist trigger already exists
> > Command: keys=pid
> > ^
> > event filter parse error: error: Invalid operator
> > Command: comm="cyclictest"
> > ^
> > event filter parse error: error: Field not found
> > Command: ((sig >= 10 && sig < 15) || dsig == 17) && comm !=
> > bash
> > ^
>
> I like this very much! One point I would like to comment is to add a
> kind of
> entry number tag, so that user distinguish the error message, e.g.
>
> # cat /sys/kernel/debug/tracing/error_log
> [1] hist:sched:sched_wakeup: error: Variable already defined
> Command: keys=pid:ts0=common_timestamp.usecs if
> comm=="cyclictest"
> ^
> [2] hist:sched:sched_waking: error: Couldn't find onmax or onchange
> variable
> Command: key=comm:p=prio:onchange($q).snapshot()
> ^
> [3] hist:sched:sched_wakeup: error: Hist trigger already exists
> Command: keys=pid
> ^
> ...
>
> What would you think?
>
I think that makes sense and would be simple to add - will do in the
next version.
Thanks,
Tom
> Thank you,
>
prev parent reply other threads:[~2019-02-14 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 18:17 [RFC PATCH v2 0/5] tracing: common error_log for ftrace Tom Zanussi
2019-02-13 18:17 ` [RFC PATCH v2 1/5] tracing: Add tracing error log Tom Zanussi
2019-02-13 18:17 ` [RFC PATCH v2 2/5] tracing: Save the last hist command's associated event name Tom Zanussi
2019-02-13 18:17 ` [RFC PATCH v2 3/5] tracing: Use tracing error_log with hist triggers Tom Zanussi
2019-02-13 18:17 ` [RFC PATCH v2 4/5] tracing: Use tracing error_log with kprobe events (incomplete) Tom Zanussi
2019-02-14 3:13 ` Masami Hiramatsu
2019-02-14 15:16 ` Tom Zanussi
2019-02-13 18:17 ` [RFC PATCH v2 5/5] tracing: Use tracing error_log with trace event filters Tom Zanussi
2019-02-13 18:27 ` [RFC PATCH v2 0/5] tracing: common error_log for ftrace Steven Rostedt
2019-02-14 3:13 ` Masami Hiramatsu
2019-02-14 15:15 ` Tom Zanussi [this message]
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=1550157323.2498.2.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).