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]

Message-ID: <20101016153229.GA6763@lenovo>
Date:	Sat, 16 Oct 2010 19:32:30 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
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, Oct 16, 2010 at 08:24:35AM +0100, Maciej W. Rozycki wrote:
> On Mon, 11 Oct 2010, Cyrill Gorcunov wrote:
> 
> > We have send_IPI_self which can't be used for NMI delivery mode (ie with
> > self shortland) but still can be used as say (didn't test)
> 
>  So what's stopping send_IPI_self() from being used for an NMI?  Can't the 
> function be updated/fixed to support these if there's a need?
> 
>   Maciej
> 

 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 :)

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