All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] tracing/ftrace: add missing wake-up on some callsites
Date: Mon, 23 Feb 2009 18:05:29 +0100	[thread overview]
Message-ID: <20090223170528.GH5961@nowhere> (raw)
In-Reply-To: <alpine.DEB.2.00.0902231151020.18221@gandalf.stny.rr.com>

On Mon, Feb 23, 2009 at 11:51:30AM -0500, Steven Rostedt wrote:
> 
> On Mon, 23 Feb 2009, Frederic Weisbecker wrote:
> > > 
> > > Perhaps we could add these callsites back, but we would need to update 
> > > trace_wake_up.
> > > 
> > > Have trace_wake_up set a flag instead, and add a tracepoint around the 
> > > scheduler (outside the grabbing of runqueue locks), that will have a 
> > > callback to the tracing code. That call back can perform the wakeups.
> > > 
> > > How does that sound?
> > 
> > 
> > That sounds good but only for these particular tracers I guess.
> 
> OK, what about making a trace_delay_wake_up()?


Which would send a delayed work to wake up?

 
> -- Steve
> 


  reply	other threads:[~2009-02-23 17:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 21:56 [PATCH] tracing/ftrace: add missing wake-up on some callsites Frederic Weisbecker
2009-02-22 22:16 ` Ingo Molnar
2009-02-23 15:37 ` Steven Rostedt
2009-02-23 15:42   ` Steven Rostedt
2009-02-23 16:26     ` Frederic Weisbecker
2009-02-23 16:51       ` Steven Rostedt
2009-02-23 17:05         ` Frederic Weisbecker [this message]
2009-02-23 17:13           ` Steven Rostedt
2009-02-23 17:34             ` Frederic Weisbecker
2009-02-23 17:37             ` Ingo Molnar
2009-02-23 18:03               ` Steven Rostedt
2009-02-23 18:09                 ` Ingo Molnar
2009-02-27 17:04                 ` Masami Hiramatsu
2009-02-23 16:22   ` 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=20090223170528.GH5961@nowhere \
    --to=fweisbec@gmail.com \
    --cc=acme@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.