From: Corey Minyard <cminyard@mvista.com>
To: vamsi@in.ibm.com
Cc: Stephen Hemminger <shemminger@osdl.org>,
Kernel List <linux-kernel@vger.kernel.org>,
lkcd-devel@lists.sourceforge.net, ak@suse.de,
vamsi_krishna@in.ibm.com
Subject: Re: [PATCH] Notifier for significant events on i386
Date: Wed, 11 Dec 2002 07:57:10 -0600 [thread overview]
Message-ID: <3DF74436.80807@mvista.com> (raw)
In-Reply-To: 20021211165153.A17546@in.ibm.com
Vamsi Krishna S . wrote:
>Andi,
>
>Isn't this a problem on x86_64 too? What is there to prevent a
>handler from being removed from the notifier list while it
>is being used to call the handler on another CPU?
>
>I am considering using a RCU-based list for notifier chains.
>Corey has done some work on these lines to add NMI notifier
>chain, I think it should be generalised on for all notifiers.
>
>Thoughts? Comments?
>
>
This is probably a good idea. I won't be able to work on it for a
while, but you can grab
my patch at http://sourceforge.net/projects/openipmi/, look under the
2.5 releases for
the most current linux-nmi-2.5.xx-vyy.diff.
-Corey
prev parent reply other threads:[~2002-12-11 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 22:02 [PATCH] Notifier for significant events on i386 Stephen Hemminger
2002-12-11 11:21 ` Vamsi Krishna S .
2002-12-11 11:16 ` William Lee Irwin III
2002-12-11 11:43 ` Vamsi Krishna S .
2002-12-11 16:56 ` [lkcd-devel] " Stephen Hemminger
2002-12-11 20:27 ` John Levon
2002-12-11 21:15 ` Alan Cox
2002-12-12 0:19 ` Stephen Hemminger
2002-12-12 7:34 ` Vamsi Krishna S .
2002-12-12 17:53 ` Stephen Hemminger
2002-12-12 17:58 ` John Levon
2002-12-13 12:32 ` Vamsi Krishna S .
2002-12-12 8:13 ` Vamsi Krishna S .
2002-12-11 13:57 ` Corey Minyard [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=3DF74436.80807@mvista.com \
--to=cminyard@mvista.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcd-devel@lists.sourceforge.net \
--cc=shemminger@osdl.org \
--cc=vamsi@in.ibm.com \
--cc=vamsi_krishna@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox