Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1675041
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks |
| Date | 2017-06-26 21:20 +0200 |
| Message-ID | <tWHIe-6lD-11@gated-at.bofh.it> (permalink) |
| References | <tWuUG-6FZ-1@gated-at.bofh.it> <tWuUG-6FZ-15@gated-at.bofh.it> <tWFwK-4Os-21@gated-at.bofh.it> <tWHyy-6h8-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 26 Jun 2017 12:02:12 -0700
Joel Fernandes <joelaf@google.com> wrote:
> >> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> >> index e7973e10398c..240c6df95ea6 100644
> >> --- a/kernel/trace/trace_events.c
> >> +++ b/kernel/trace/trace_events.c
> >> @@ -343,6 +343,28 @@ void trace_event_enable_cmd_record(bool enable)
> >> mutex_unlock(&event_mutex);
> >> }
> >>
> >> +void trace_event_enable_tgid_record(bool enable)
> >
> > This should return a value.
> >
> >> +{
> >> + struct trace_event_file *file;
> >> + struct trace_array *tr;
> >> +
> >> + mutex_lock(&event_mutex);
> >> + do_for_each_event_file(tr, file) {
> >> + if (!(file->flags & EVENT_FILE_FL_ENABLED))
> >> + continue;
> >> +
> >> + if (enable) {
> >> + tracing_start_tgid_record();
> >
> > If we fail to start, the bit should not be set, and we should return
> > failure. Note, it can only fail on the first try, as once it is
> > allocated, you don't need to worry about it failing. Thus, if it fails,
> > break out of the loop now and return failure.
> >
>
> That seems Ok with me to do, I think a valid point.
>
> I think that I should do it in the second call to
> tracing_start_tgid_record too then (__ftrace_event_enable_disable) to
> error out if the allocation fails.
>
> While going this code I again, I noticed another potential issue in
> __ftrace_event_enable_disable
Thinking about this more. Just allocate the array as soon as the option
is enabled, regardless if an trace event is set. That will make it a
lot simpler. If it fails to allocate, you can simply bail out with
-ENOMEM, and the setting of the option will return that. Then we can
even remove the WARN_ONCE() at allocation failure, as the user will
know what happened.
-- Steve
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v4 0/3] tracing: Add support for recording tgid of tasks Joel Fernandes <joelaf@google.com> - 2017-06-26 07:40 +0200
[PATCH v4 3/3] tracing/ftrace: Add support to record and display tgid Joel Fernandes <joelaf@google.com> - 2017-06-26 07:40 +0200
Re: [PATCH v4 3/3] tracing/ftrace: Add support to record and display tgid Joel Fernandes <joelaf@google.com> - 2017-06-27 05:20 +0200
[PATCH v4 1/3] tracing: Add support for recording tgid of tasks Joel Fernandes <joelaf@google.com> - 2017-06-26 07:40 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Steven Rostedt <rostedt@goodmis.org> - 2017-06-26 19:00 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Steven Rostedt <rostedt@goodmis.org> - 2017-06-26 21:10 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Joel Fernandes <joelaf@google.com> - 2017-06-26 21:10 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Joel Fernandes <joelaf@google.com> - 2017-06-26 21:20 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Steven Rostedt <rostedt@goodmis.org> - 2017-06-26 21:30 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Joel Fernandes <joelaf@google.com> - 2017-06-26 21:20 +0200
Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks Steven Rostedt <rostedt@goodmis.org> - 2017-06-26 21:20 +0200
[PATCH v4 2/3] tracing: Add support for display of tgid in trace output Joel Fernandes <joelaf@google.com> - 2017-06-26 07:40 +0200
csiph-web