From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Jon Masters <jonathan@jonmasters.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: try_module_get and friends
Date: Fri, 7 Mar 2008 08:16:55 -0800 [thread overview]
Message-ID: <20080307161655.GB9033@linux.vnet.ibm.com> (raw)
In-Reply-To: <1204751702.17630.27.camel@localhost.localdomain>
On Wed, Mar 05, 2008 at 01:15:02PM -0800, Daniel Walker wrote:
>
> On Wed, 2008-03-05 at 15:54 -0500, Steven Rostedt wrote:
>
> > Actually, we were simply thinking of calling an rcu_lock before checking
> > the handlers, and releasing the lock when all are done. Then before doing
> > the module unload, we do a rcu_sync. Note, no interrupt handler should
> > ever do a rcu_sync.
>
> There's already some smp synchronize inside free_irq, are you sure
> that's not already handling this for smp? For -rt we could just enable
> it for UP ..
If (desc->status & IRQ_INPROGRESS) remains true throughout the
execution of the threaded (and thus preemptible) interrupt handler,
then the synchronize_irq() should do the trick.
Thanx, Paul
next prev parent reply other threads:[~2008-03-07 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 5:20 try_module_get and friends Jon Masters
2008-03-04 5:28 ` Jon Masters
2008-03-04 20:07 ` Jon Masters
2008-03-05 19:30 ` Daniel Walker
2008-03-05 19:47 ` Steven Rostedt
2008-03-05 20:28 ` Daniel Walker
2008-03-05 20:46 ` Frank Ch. Eigler
2008-03-05 20:54 ` Steven Rostedt
2008-03-05 21:15 ` Daniel Walker
2008-03-07 16:16 ` Paul E. McKenney [this message]
2008-03-05 21:14 ` Steven Rostedt
2008-03-10 5:53 ` Jon Masters
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=20080307161655.GB9033@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dwalker@mvista.com \
--cc=fche@redhat.com \
--cc=jonathan@jonmasters.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.