linux-kernel - Re: [RFC] x86, NMI, Treat unknown NMI as hardware error

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: <20110517175707.GP31888@redhat.com>
Date:	Tue, 17 May 2011 13:57:07 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Huang Ying <ying.huang@...el.com>,
	Cyrill Gorcunov <gorcunov@...il.com>,
	huang ying <huang.ying.caritas@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Robert Richter <robert.richter@....com>
Subject: Re: [RFC] x86, NMI, Treat unknown NMI as hardware error

On Tue, May 17, 2011 at 09:38:47AM -0700, Andi Kleen wrote:
> > Can we agree on this, that if an OEM implemented HEST properly such that a
> > hardware error happens it will generate a GHES record.  The subsequent NMI
> 
> Apparently there are some (rare) corner cases where it's hard/impossible
> to do. So in those cases you will see an NMI without record.

Hmm, I would be interested to know what kind, but it doesn't matter I
guess.

> 
> In the "normal" error case you will a GHES record on NMI.

Random thought, in the Firmware first mode of HEST (which is the only way
GHES records get produced??), does an SCI happen first to jump into the
firmware for processing, then an NMI?

Cheers,
Don
--
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/