[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DD22480.7090309@intel.com>
Date: Tue, 17 May 2011 15:32:16 +0800
From: Huang Ying <ying.huang@...el.com>
To: Cyrill Gorcunov <gorcunov@...il.com>
CC: huang ying <huang.ying.caritas@...il.com>,
Ingo Molnar <mingo@...e.hu>, Don Zickus <dzickus@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andi Kleen <andi@...stfloor.org>,
Robert Richter <robert.richter@....com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [RFC] x86, NMI, Treat unknown NMI as hardware error
On 05/17/2011 03:44 AM, Cyrill Gorcunov wrote:
> On 05/16/2011 05:09 AM, Huang Ying wrote:
> ...
>>>
>>> I'm personally fine even if it's enabled by default, only worried to have
>>> an option to disable hwerr from boot line.
>>
>> The white list mechanism is not sufficient? Spurious unknown NMI can
>> occur on white list machines? People don't want to protect their data?
>>
>
> I suppose no, it's not sufficient considering how many cpu errata already
> out in general. And I see no guarantee that unknown NMIs never triggers on
> white list machines and I know that you know that as well ;)
I write this patch because I believe white listed machines will not
generate unknown NMI for no good reason ;)
If we just want to push the unknown NMI logic to user space, existing
"unknown_nmi_panic" is sufficient.
Best Regards,
Huang Ying
--
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