From: Prarit Bhargava <prarit@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"Luck, Tony" <tony.luck@intel.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 v2 1/2] x86: mce: kexec: turn off MCE in kexec
Date: Mon, 02 Mar 2015 11:50:49 -0500 [thread overview]
Message-ID: <54F494E9.4020307@redhat.com> (raw)
In-Reply-To: <20150302163216.GF17521@pd.tnic>
On 03/02/2015 11:32 AM, Borislav Petkov wrote:
> On Mon, Mar 02, 2015 at 11:33:33PM +0900, Naoya Horiguchi wrote:
>> Yes, CPU offlining is one option to keep other CPUs quiet. I'm not sure why
>> current kexec implementation doesn't offline the other CPUs but just doing
>> cpu_relax() loop, but my guess is that in some kernel panic situation (like
>> soft lockup) we want to keep CPUs' status undisturbed to make sure the bug's
>> info is captured in kdump.
>
> Well either offlining or keeping them in the idle loop is fine - they're
> not executing anything else and thus the probability of them causing an
> MCE becomes disappearingly small.
Unless entering a deep C state kicks an MCE ... which we've seen with flaky
hardware.
P.
>
next prev parent reply other threads:[~2015-03-02 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 4:58 [PATCH v2 1/2] x86: mce: kexec: turn off MCE in kexec Naoya Horiguchi
2015-02-27 4:58 ` [PATCH v2 2/2] x86: mce: comment about MCE synchronization timeout on definition of tolerant Naoya Horiguchi
2015-02-27 11:09 ` [PATCH v2 1/2] x86: mce: kexec: turn off MCE in kexec Prarit Bhargava
2015-02-27 12:06 ` Borislav Petkov
2015-02-27 18:27 ` Luck, Tony
2015-03-02 2:31 ` Naoya Horiguchi
2015-03-02 12:17 ` Borislav Petkov
2015-03-02 14:33 ` Naoya Horiguchi
2015-03-02 16:32 ` Borislav Petkov
2015-03-02 16:50 ` Prarit Bhargava [this message]
2015-03-02 17:25 ` Borislav Petkov
2015-02-27 12:46 ` Naoya Horiguchi
2015-02-27 13:14 ` Prarit Bhargava
2015-03-02 2:16 ` 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=54F494E9.4020307@redhat.com \
--to=prarit@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox