From: Andi Kleen <ak@linux.intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Huang Ying <ying.huang@intel.com>,
Jin Dongming <jin.dongming@np.css.fujitsu.com>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [Patch-next] Remove notify_die in do_machine_check functioin
Date: Thu, 27 May 2010 08:57:37 +0200 [thread overview]
Message-ID: <4BFE17E1.7020103@linux.intel.com> (raw)
In-Reply-To: <4BFE0BE1.4040408@jp.fujitsu.com>
, Hidetoshi Seto wrote:
> (2010/05/27 12:21), Huang Ying wrote:
>> I have heard about that on some machine, some hardware error output pin
>> of chipset may be linked with some input pin of CPU which can cause MCE.
>> That is, MCE is used to report some chipset errors too. I think that is
>> why notify_die is called in do_machine_check. Simply removing notify_die
>> is not good for these machines.
>
> Hum, it sounds like "notify_die here is hook for proprietary chipset
> driver". Anyone who have such machine and driver in real?
No, the die hook was to be compatible with the old KDB patchkit
which hooked into MCE too.
> Problems are (1) many callbacks will behave wrongly since they don't
> aware that DIE_NMI event can be posted from Machine Check, and (2)
> if the machine is not such special hardware it is just waste of time
> in critical context where quick page-poisoning might be required.
Yes the best action is probably to just remove it right now.
> One quick alternative is define "DIE_MCE" and use it instead, but
> if special hook like this is really required, I suppose we should
> invent some special interface for external plug-in like a chipset's
> LLHEH (low-level hardware error handler) etc., to allow additional
> platform-specific error handling in critical context.
I don't think we need or want that.
-Andi
next prev parent reply other threads:[~2010-05-27 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 2:40 [Patch-next] Remove notify_die in do_machine_check functioin Jin Dongming
2010-05-27 3:21 ` Huang Ying
2010-05-27 6:06 ` Hidetoshi Seto
2010-05-27 6:57 ` Andi Kleen [this message]
2010-05-27 6:54 ` Andi Kleen
2010-05-27 11:04 ` Alan Cox
2010-05-27 13:15 ` Andi Kleen
2010-05-27 6:58 ` Andi Kleen
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=4BFE17E1.7020103@linux.intel.com \
--to=ak@linux.intel.com \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=ying.huang@intel.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