public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/ftrace: stop {irqs,preempt}soff tracers when tracing is stopped
Date: Tue, 17 Mar 2009 23:54:55 +0100	[thread overview]
Message-ID: <20090317225454.GA5143@nowhere> (raw)
In-Reply-To: <alpine.DEB.2.00.0903171757320.9036@gandalf.stny.rr.com>

On Tue, Mar 17, 2009 at 05:59:22PM -0400, Steven Rostedt wrote:
> 
> On Tue, 17 Mar 2009, Frederic Weisbecker wrote:
> > > > +	/*
> > > > +	 * Stop the tracer to avoid a warning subsequent
> > > > +	 * to buffer flipping failure because tracing_stop()
> > > > +	 * disables the tr and max buffers, making flipping impossible
> > > > +	 * in case of parallels max preempt off latencies.
> > > > +	 */
> > > > +	trace->stop(tr);
> > > >  	/* stop the tracing. */
> > > >  	tracing_stop();
> > > 
> > > I'm actually thinking that tracing_stop() should call the current tracer
> > > "stop" function.
> > > 
> > > -- Steve
> > 
> > 
> > Indeed, it could be better.
> > But I think of a combination of stop() callback call plus
> > ring buffer disabled because I'm not sure all tracers implement
> > the stop callback.
> 
> Yes, that's what I meant. The tracing_stop should do a few things, and one
> of them is to call the stop function if it exists.
> 
> > 
> > Should I send a v2 based on the above?
> 
> Sure.
> 
> -- Steve


Ingo,

I tested the call to the start/stop callbacks from tracing_start() and tracing_stop()
but it's not possible for now: the sched_switch tracer register/unregister his
tracepoints from these callbacks, thus allocate some memory. But tracing_start/stop
can be called from atomic.

I discussed about that with Steven on irc, and for now the v1 should be applied
as a temporary solution. We plan to simplify later the start/stop callbacks from
each tracers that need it.

Thanks.


  reply	other threads:[~2009-03-17 22:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1237325938-5240-1-git-send-email-fweisbec@gmail.com>
2009-03-17 21:46 ` [PATCH] tracing/ftrace: stop {irqs,preempt}soff tracers when tracing is stopped Steven Rostedt
2009-03-17 21:49   ` Frederic Weisbecker
2009-03-17 21:59     ` Steven Rostedt
2009-03-17 22:54       ` Frederic Weisbecker [this message]
2009-03-18  8:59         ` Ingo Molnar
2009-03-18  9:18           ` Ingo Molnar
2009-03-18  9:29             ` Ingo Molnar
2009-03-18 14:31             ` Steven Rostedt
2009-03-18 14:00           ` Steven Rostedt
2009-03-18  9:19 ` [tip:tracing/ftrace] tracing/ftrace: stop {irqs, preempt}soff " Frederic Weisbecker

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=20090317225454.GA5143@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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