From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Asselstine <mark.asselstine@windriver.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] trace-cmd: setting plugin to 'nop' clears data before its recorded
Date: Fri, 06 Apr 2012 08:24:53 -0400 [thread overview]
Message-ID: <1333715093.23090.2.camel@pippen.local.home> (raw)
In-Reply-To: <9754868.ceVoCaPqDZ@super-penguin>
On Fri, 2012-04-06 at 08:06 -0400, Mark Asselstine wrote:
> Works for me. I see you make use of gboolean elsewhere so I assume you prefer
> the use of this rather than using int?
Sure.
>
> > Also, and this has nothing to do with you or your patches, I simply hate
> > the fact that I called these plugins. They should have been called
> > "tracers" but I think I'm stuck with it. The term now is ambiguous as it
> > means both a tracer (as it does here) and it means actual plugins that
> > you can load into trace-cmd itself.
> >
>
> To stop the proliferation do you want me to name the bool
> 'disable_current_tracer' rather than 'disable_plugin' or 'plugin'?
disable_tracer would due.
>
>
> > > {
> > >
> > > disable_tracing();
> > >
> > > - set_plugin("nop");
> > >
> > > reset_events();
> > >
> > > /* Force close and reset of ftrace pid file */
> > >
> > > @@ -911,6 +910,12 @@ static void disable_all(void)
> > >
> > > clear_trace();
> > >
> > > }
> > >
> > > +static void disable_all(void)
> > > +{
> > > + disable_all_but_plugin();
> > > + set_plugin("nop");
> > > +}
> > > +
> > >
> > > static void
> > > update_sched_event(struct event_list **event, const char *file,
> > >
> > > const char *pid_filter, const char *field_filter)
> > >
> > > @@ -2227,7 +2232,7 @@ void trace_record (int argc, char **argv)
> > >
> > > }
> > >
> > > if (!keep)
> > >
> > > - disable_all();
> > > + disable_all_but_plugin();
> > >
> > > printf("Kernel buffer statistics:\n"
> > >
> > > " Note: \"entries\" are the entries left in the
> > > kernel ring buffer and are not\n">
> > > @@ -2245,6 +2250,8 @@ void trace_record (int argc, char **argv)
> > >
> > > record_data(date2ts);
> > > delete_thread_data();
> > >
> > > + if (!keep)
> > > + set_plugin("nop");
> > >
> > > if (keep)
> > >
> > > exit(0);
> >
> > I think the above would have been better if you did:
> >
> > if (keep)
> > exit(0);
> > else
> > set_plugin(nop);
> >
> > -- Steve
>
> Wow, I wasn't being too bright there was I? Agreed and the 'else' isn't
> necessary either, so this is a good cleanup.
>
> I will get this fixed up later today. Do you want a V2 of the full patch series
> or just an update of this one patch?
You can just update this patch with a v2 on it. I'm currently traveling
home from a conference and wont be back to work till Tuesday. Please,
take your time.
Thanks!
-- Steve
next prev parent reply other threads:[~2012-04-06 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 19:19 [PATCH 0/3] trace-cmd fixes for latency tracing record and report Mark Asselstine
2012-04-05 19:19 ` [PATCH 1/3] trace-cmd: add checks for invalid pointers to fix segfaults Mark Asselstine
2012-04-05 19:19 ` [PATCH 2/3] trace-cmd: don't call stop_threads() if doing latency tracing Mark Asselstine
2012-04-05 19:19 ` [PATCH 3/3] trace-cmd: setting plugin to 'nop' clears data before its recorded Mark Asselstine
2012-04-05 21:37 ` Steven Rostedt
2012-04-06 12:06 ` Mark Asselstine
2012-04-06 12:24 ` Steven Rostedt [this message]
2012-04-08 15:38 ` [PATCH v2 3/3] trace-cmd: setting plugin to 'nop' clears data before it's recorded Mark Asselstine
2012-05-23 9:33 ` Steven Rostedt
2012-05-23 13:26 ` Mark Asselstine
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=1333715093.23090.2.camel@pippen.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.asselstine@windriver.com \
/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®