From: Huang Ying <ying.huang@intel.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: huang ying <huang.ying.caritas@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Don Zickus <dzickus@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Robert Richter <robert.richter@amd.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [RFC] x86, NMI, Treat unknown NMI as hardware error
Date: Tue, 17 May 2011 15:32:16 +0800 [thread overview]
Message-ID: <4DD22480.7090309@intel.com> (raw)
In-Reply-To: <4DD17EAF.4040305@gmail.com>
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
next prev parent reply other threads:[~2011-05-17 7:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 8:23 Huang Ying
2011-05-13 12:45 ` Don Zickus
2011-05-13 13:00 ` Ingo Molnar
2011-05-13 13:24 ` huang ying
2011-05-13 15:20 ` Ingo Molnar
2011-05-13 16:00 ` Don Zickus
2011-05-16 11:29 ` Ingo Molnar
2011-05-16 19:19 ` Don Zickus
2011-05-17 8:50 ` Ingo Molnar
2011-05-17 7:41 ` Huang Ying
2011-05-17 8:53 ` Ingo Molnar
2011-05-19 6:44 ` Huang Ying
2011-05-20 11:58 ` Ingo Molnar
2011-05-14 0:56 ` huang ying
2011-05-13 13:17 ` huang ying
2011-05-13 13:51 ` Don Zickus
2011-05-14 0:20 ` huang ying
2011-05-14 4:11 ` Andi Kleen
2011-05-13 15:17 ` Cyrill Gorcunov
2011-05-14 0:26 ` huang ying
2011-05-14 7:51 ` Cyrill Gorcunov
2011-05-15 0:06 ` huang ying
2011-05-15 6:34 ` Cyrill Gorcunov
2011-05-16 1:09 ` Huang Ying
2011-05-16 19:03 ` Don Zickus
2011-05-16 19:53 ` Cyrill Gorcunov
2011-05-17 5:39 ` Huang Ying
2011-05-17 14:24 ` Don Zickus
2011-05-17 16:38 ` Andi Kleen
2011-05-17 17:57 ` Don Zickus
2011-05-17 18:18 ` Andi Kleen
2011-05-17 19:07 ` Don Zickus
2011-05-20 8:13 ` Huang Ying
2011-06-09 12:09 ` Don Zickus
2011-06-09 15:22 ` Cyrill Gorcunov
2011-06-13 1:34 ` Huang Ying
2011-05-16 19:44 ` Cyrill Gorcunov
2011-05-17 7:32 ` Huang Ying [this message]
2011-05-14 0:47 ` huang ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD22480.7090309@intel.com \
--to=ying.huang@intel.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=gorcunov@gmail.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome