[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110517190738.GH29881@redhat.com>
Date: Tue, 17 May 2011 15:07:38 -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 11:18:59AM -0700, Andi Kleen wrote:
> > 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?
>
> Either that or there is a separate service processor which handles it.
> Presumably it depends a lot on the particular system.
Ah interesting. I was going to suggest somehow setting a bit when an SCI
comes in and check that bit in the unknown NMI path as a possible hint
that the NMI might be related to HEST (sorta how we flag unknown NMIs in
the perf code).
It was just an idea. Obviously a service processor will make that more
difficult. :-)
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/
Powered by blists - more mailing lists