All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org, edwardsg@sgi.com,
	dipankar@in.ibm.com
Subject: Re: contention on profile_lock
Date: Thu, 4 Nov 2004 12:49:21 -0800	[thread overview]
Message-ID: <200411041249.21718.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20041104201257.GA14786@holomorphy.com>

On Thursday, November 4, 2004 12:12 pm, William Lee Irwin III wrote:
> On Thu, Nov 04, 2004 at 11:56:23AM -0800, Jesse Barnes wrote:
> > ..but since I haven't heard from Dipankar, here's a patch that removes
> > the profile_hook notifier list altogether in favor of a simple flag that
> > controls whether or not to call the oprofile timer routine directly. 
> > Does it look ok?
>
> This looks reasonable to me.

John pointed out that this breaks modules.  Would registering and 
unregistering a function pointer thus be module safe?  Dipankar, hopefully 
you have something better?

static int timer_start(void)
{
 /* Setup the callback pointer */
 oprofile_timer_notify = oprofile_timer;
 return 0;
}


static void timer_stop(void)
{
 /* Tear down the callback pointer after sync_kernel */
 synchronize_kernel();
 oprofile_timer_notify = NULL;
}

Thanks,
Jesse

  reply	other threads:[~2004-11-04 21:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 19:52 contention on profile_lock Jesse Barnes
2004-11-02 20:02 ` Jack Steiner
2004-11-02 21:42   ` Jesse Barnes
2004-11-04 19:56     ` Jesse Barnes
2004-11-04 20:12       ` William Lee Irwin III
2004-11-04 20:49         ` Jesse Barnes [this message]
2004-11-04 21:51           ` John Levon
2004-11-04 22:08             ` Jesse Barnes
2004-11-04 21:55           ` Jesse Barnes
2004-11-04 22:16             ` Dipankar Sarma
2004-11-04 22:21             ` John Levon
2004-11-04 22:27               ` Jesse Barnes
2004-11-04 22:52                 ` John Levon

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=200411041249.21718.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=dipankar@in.ibm.com \
    --cc=edwardsg@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=wli@holomorphy.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 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.