From: Alan Robertson <alanr@unix.sh>
To: "Isabelle, Francois" <Francois.Isabelle@ca.kontron.com>
Cc: "Linux-Ha (E-mail)" <linux-ha@muc.de>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Handling NMI in a kernel module
Date: Fri, 26 Jul 2002 15:55:16 -0600 [thread overview]
Message-ID: <3D41C544.9090702@unix.sh> (raw)
In-Reply-To: 5009AD9521A8D41198EE00805F85F18F219A7E@sembo111.teknor.com
Isabelle, Francois wrote:
> Is it possible to request_nmi() the way you can request_irq() from a kernel
> driver on the i386 arch?
>
> Our hardware watchdog is dual stage and can generate NMI on first stage ,
> our cPCI handle switch can also be used for Hot swap request via NMI.
> I'ld like to make use of this, I noticed cpqhealth module already
> implemented some nmi handling but this driver is close sourced.
>
> Should we patch in i386/kernel/traps.c to add a callback to our stuff in
> unkown_nmi_error().
>
> I'ld like my driver to register a callback there, what about maintaining a
> list of user callback functions which could be registered via:
>
> request_nmi(int option, void (*hander)(void *dev_id, struct pt_regs *regs),
> unsigned long flags, const char *dev_name, void *dev_id);
>
> where option could take meaning such as
> - prepend : place at start of nmi callback functions
> - append : place at end of nmi callback functions
> - truncate : replace callback chain
>
> Is there any standard mecanism to implement such features( dual stage
> watchdog ) ?
We've created a separate mailing list to talk about enhancements to the
watchdog driver API. Dual stage watchdog is on the list. It's pretty quiet
now, but perhaps now that summer is winding down, we can get started again...
Info on the list is here:
http://lists.tummy.com/mailman/listinfo/watchdogng
-- Alan Robertson
alanr@unix.sh
next prev parent reply other threads:[~2002-07-26 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 17:37 Handling NMI in a kernel module Isabelle, Francois
2002-07-23 18:27 ` John Levon
2002-07-23 22:30 ` Alan Cox
2002-07-26 21:55 ` Alan Robertson [this message]
2002-07-27 2:05 ` Alan Cox
2002-07-27 3:30 ` Alan Robertson
2002-07-27 12:39 ` Alan Cox
2002-07-27 13:50 ` Alan Robertson
2002-07-27 3:44 ` Jonathan Lundell
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=3D41C544.9090702@unix.sh \
--to=alanr@unix.sh \
--cc=Francois.Isabelle@ca.kontron.com \
--cc=linux-ha@muc.de \
--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