linux-kernel - Re: [RFC] arch generic way to trigger unknown NMIs

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 16 Oct 2010 17:15:16 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Cyrill Gorcunov <gorcunov@...il.com>
cc:	Don Zickus <dzickus@...hat.com>, Andi Kleen <andi@...stfloor.org>,
	mingo@...e.hu, fweisbec@...il.com, robert.richter@....com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] arch generic way to trigger unknown NMIs

On Sat, 16 Oct 2010, Cyrill Gorcunov wrote:

>  Hi Maciej, the send_IPI_self could be modified to send NMI (at moment it
> uses self shortcut with fixed delivery mode). The question is rather if
> we need it without a real caller yet. When Don's patch gets merged we
> will have a real caller then and could update send_IPI_self to support
> NMI delivery mode. Something like that :)

 Sounds backwards to me.  My understanding is a need has just arisen, so 
why not:

1. Update send_IPI_self().

2. Add code that makes use of the new functionality.

3. Submit all the changes as self-contained patches in a single series to 
   be applied at the same time.

?  That's what I'd imagine the most natural way of doing this would be.

  Maciej
--
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/