From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Junichi Nomura <j-nomura@ce.jp.nec.com>,
Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Subject: Re: [PATCH 1/2] x86: mce: kdump: use under_crashdumping to turn off MCE in all CPUs together
Date: Tue, 24 Feb 2015 19:40:33 +0100 [thread overview]
Message-ID: <20150224184033.GL3420@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F329EB977@ORSMSX114.amr.corp.intel.com>
On Tue, Feb 24, 2015 at 06:20:16PM +0000, Luck, Tony wrote:
> I'm not sure - the broadcast MCE will still arrive at that cpu - and
> with CR4.MCE==0, it will shutdown. Not sure if that just affects that
> logical thread, or if it pulls a signal line to take down the whole
> machine.
If that is the case, the tolerance level might be the better approach
after all...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-02-24 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 9:12 [PATCH 1/2] x86: mce: kdump: use under_crashdumping to turn off MCE in all CPUs together Naoya Horiguchi
2015-02-23 9:12 ` [PATCH 2/2] x86: mce: comment about MCE synchronization timeout on definition of tolerant Naoya Horiguchi
2015-02-23 9:27 ` [PATCH 1/2] x86: mce: kdump: use under_crashdumping to turn off MCE in all CPUs together Borislav Petkov
2015-02-23 13:01 ` Naoya Horiguchi
2015-02-23 13:58 ` Borislav Petkov
2015-02-23 15:41 ` Naoya Horiguchi
2015-02-23 17:06 ` Borislav Petkov
2015-02-24 8:15 ` Naoya Horiguchi
2015-02-24 9:56 ` Borislav Petkov
2015-02-24 18:20 ` Luck, Tony
2015-02-24 18:40 ` Borislav Petkov [this message]
2015-02-24 18:47 ` Luck, Tony
2015-02-24 21:19 ` Borislav Petkov
2015-02-25 0:54 ` Naoya Horiguchi
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=20150224184033.GL3420@pd.tnic \
--to=bp@alien8.de \
--cc=j-nomura@ce.jp.nec.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=nao.horiguchi@gmail.com \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.