From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Namhyung Kim <namhyung@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: [RFC][PATCH 0/3] tracing: Make error_log per instance
Date: Tue, 02 Apr 2019 15:42:16 -0500 [thread overview]
Message-ID: <1554237736.11284.4.camel@kernel.org> (raw)
In-Reply-To: <20190402182951.130809543@goodmis.org>
Hi Steve,
On Tue, 2019-04-02 at 14:29 -0400, Steven Rostedt wrote:
> Hi Tom,
>
> I noticed that you created an error_log file in every instance, but
> they all show the same errors. These three patches make it so that
> the errors appear in the instance directory that they happened in.
> If you write a bad error to
>
> /sys/kernel/tracing/instance/foo/events/sched/sched_switch/hist
>
> It appears only in
>
> /sys/kernel/tracing/instances/foo/error_log
>
> Which I think is the proper approach, especially instances should not
> affect the top directory or other instances.
>
> For those errors that do not have an associated instance (creating a
> kprobe/uprobe event or perf), a NULL passed to tracing_log_err() will
> result in the error message in the top level error message.
>
> Do you (or Masami) have any issues with this patch set?
>
> If not, please add a "reviewed-by" or "acked-by" and I'll add it
> to your patch series and push them to for-next (after more testing).
>
Looks good, thanks for doing this. You can add my:
Reviewed-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Tested-by: Tom Zanussi <tom.zanussi@linux.intel.com>
FYI, I noticed one bit of trailing whitespace in 2/3 - you might want
to run it through checkpatch again before you merge ;-)
Thanks,
Tom
> If this isn't obvious, this patch series is on top of:
>
> http://lkml.kernel.org/r/cover.1554072478.git.tom.zanussi@linux.int
> el.com
>
> Actually, I added it right after patch 5 of that series (before the
> selftests and documentation).
>
> Thanks!
>
> -- Steve
>
>
>
> Steven Rostedt (VMware) (3):
> tracing: Add trace_array parameter to create_event_filter()
> tracing: Have histogram code pass around trace_array for error
> handling
> tracing: Have the error logs show up in the proper instances
>
> ----
> kernel/trace/trace.c | 55 +++++++++-----
> kernel/trace/trace.h | 8 +-
> kernel/trace/trace_events_filter.c | 25 ++++---
> kernel/trace/trace_events_hist.c | 145 ++++++++++++++++++++----
> ------------
> kernel/trace/trace_events_trigger.c | 3 +-
> kernel/trace/trace_probe.c | 2 +-
> 6 files changed, 142 insertions(+), 96 deletions(-)
next prev parent reply other threads:[~2019-04-02 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 18:29 [RFC][PATCH 0/3] tracing: Make error_log per instance Steven Rostedt
2019-04-02 18:29 ` [RFC][PATCH 1/3] tracing: Add trace_array parameter to create_event_filter() Steven Rostedt
2019-04-02 18:29 ` [RFC][PATCH 2/3] tracing: Have histogram code pass around trace_array for error handling Steven Rostedt
2019-04-02 18:29 ` [RFC][PATCH 3/3] tracing: Have the error logs show up in the proper instances Steven Rostedt
2019-04-02 20:42 ` Tom Zanussi [this message]
2019-04-02 20:57 ` [RFC][PATCH 0/3] tracing: Make error_log per instance Steven Rostedt
2019-04-08 0:08 ` Masami Hiramatsu
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=1554237736.11284.4.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).