public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Patch to 2.6.8.1-mm2 to allow multiple NMI handlers to be registered
Date: Thu, 19 Aug 2004 14:27:56 -0500	[thread overview]
Message-ID: <4124FF3C.6080108@acm.org> (raw)
In-Reply-To: <20040819164049.GS8967@schnapps.adilger.int>

Andreas Dilger wrote:

>On Aug 19, 2004  09:35 -0500, Corey Minyard wrote:
>  
>
>>* Allow multiple handlers to be registered and return if they have 
>>handled the NMI or not.  oprofile and nmi_watchdog are modified to use this.
>>    
>>
>
>Why not use a notifier call chain as is done with panic & friends instead
>of implementing the same thing specifically for NMI?
>
>  
>
A couple of reasons:

* The "handled" value needs to be passed around so handler know if 
previous handlers have already handled the NMI.
* It allows the list of registered NMI handlers to be dumped in 
/proc/interrupts

I thought that the notifiers callout used locks (which would be a 
no-go), but it doesn't.  So I can scratch that one from my list.

Thanks,

-Corey

  reply	other threads:[~2004-08-19 19:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 14:35 Patch to 2.6.8.1-mm2 to allow multiple NMI handlers to be registered Corey Minyard
2004-08-19 15:29 ` Mikael Pettersson
2004-08-19 16:16   ` Corey Minyard
2004-08-19 16:27     ` Mikael Pettersson
2004-08-19 16:45       ` Andreas Schwab
2004-08-19 16:31     ` John Levon
2004-08-20 22:42       ` Zwane Mwaikambo
2004-08-19 19:15   ` Corey Minyard
2004-08-19 16:40 ` Andreas Dilger
2004-08-19 19:27   ` Corey Minyard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-21 10:26 Mikael Pettersson

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=4124FF3C.6080108@acm.org \
    --to=minyard@acm.org \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.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