public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip 1/1] tracing: handle unregistering the current tracer
Date: Mon, 9 Feb 2009 12:58:25 +0100	[thread overview]
Message-ID: <20090209115825.GA17782@elte.hu> (raw)
In-Reply-To: <20090209115151.GB5265@ghostprotocols.net>


* Arnaldo Carvalho de Melo <acme@redhat.com> wrote:

> Em Mon, Feb 09, 2009 at 10:58:16AM +0100, Ingo Molnar escreveu:
> > 
> > * Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> > 
> > > Impact: simplification
> > > 
> > > Instead of requiring that plugins have the sequence:
> > > 
> > >   my_tracer_stop(my_trace_array);
> > >   unregister_tracer(my_tracer);
> > > 
> > > it should be possible just do a:
> > > 
> > >   unregister_tracer(my_tracer);
> > > 
> > > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> > > ---
> > >  kernel/trace/trace.c |    9 +++++++++
> > >  1 files changed, 9 insertions(+), 0 deletions(-)
> > 
> > Applied to tip/tracing/ftrace, thanks Arnaldo!
> > 
> > Nice one - we should try to shoot for the smallest physically
> > possible linecount for any new (possibly trivial) tracer plugin.
> 
> That and also for as few as possible EXPORT_SYMBOL_GPL entries, now, for
> converting net/ipv4/tcp_probe.c to an ftrace plugin + one tracepoint at
> tcp_rcv_established we need:
> 
> doppio linux-2.6-tip]$ grep ^+EXPORT_SYMBOL ~/tcp_cwnd_tracer.patch 
> +EXPORT_SYMBOL_GPL(register_tracer);
> +EXPORT_SYMBOL_GPL(unregister_tracer);
> +EXPORT_SYMBOL_GPL(tracing_record_cmdline);
> +EXPORT_SYMBOL_GPL(trace_buffer_lock_reserve);
> +EXPORT_SYMBOL_GPL(trace_buffer_unlock_commit);
> +EXPORT_SYMBOL_GPL(trace_seq_printf);
> +EXPORT_SYMBOL_GPL(register_ftrace_event);
> +EXPORT_SYMBOL_GPL(unregister_ftrace_event);
> [acme@doppio linux-2.6-tip]$

ok. For in-kernel plugins it's of course fine to do those exports in any case.

	Ingo

      reply	other threads:[~2009-02-09 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07 20:52 [PATCH tip 1/1] tracing: handle unregistering the current tracer Arnaldo Carvalho de Melo
2009-02-09  9:58 ` Ingo Molnar
2009-02-09 11:51   ` Arnaldo Carvalho de Melo
2009-02-09 11:58     ` Ingo Molnar [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=20090209115825.GA17782@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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