linux-kernel - RE: [PATCH 1/2] watchdog, hpwdt: Remove priority option for NMI callback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1331314389.18960.1.camel@twins>
Date:	Fri, 09 Mar 2012 18:33:09 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	"Mingarelli, Thomas" <Thomas.Mingarelli@...com>
Cc:	Don Zickus <dzickus@...hat.com>, "x86@...nel.org" <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Wim Van Sebroeck <wim@...ana.be>
Subject: RE: [PATCH 1/2] watchdog, hpwdt: Remove priority option for NMI
 callback

On Fri, 2012-03-09 at 17:28 +0000, Mingarelli, Thomas wrote:
> Can I register for more than one type? Like NMI_UNKNOWN | NMI_DIE (or
> something like that)?

There's only NMI_LOCAL and NMI_UNKNOWN, and you can only use NMI_LOCAL
if you can tell you generated the NMI. See it as one massively shared
interrupt line.

The NMI_UNKNOWN handler is basically the handler of last resort for
those that cannot multiplex the line, hence the restriction of only
having one.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/