mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xunlei Pang <xpang@redhat.com>
To: "Luck, Tony" <tony.luck@intel.com>,
	"xlpang@redhat.com" <xlpang@redhat.com>,
	Borislav Petkov <bp@alien8.de>
Cc: Prarit Bhargava <prarit@redhat.com>,
	Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Junichi Nomura <j-nomura@ce.jp.nec.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Dave Young <dyoung@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/mce: Keep quiet in case of broadcasted mce after system panic
Date: Wed, 22 Feb 2017 13:50:47 +0800	[thread overview]
Message-ID: <58AD26B7.5070602@redhat.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3A2BE9B1@ORSMSX114.amr.corp.intel.com>

On 02/22/2017 at 02:20 AM, Luck, Tony wrote:
>> It's from my understanding, I didn't get the explicit description from the intel SDM on this point.
>> If a broadcast SRAO comes on real hardware, will MSR_IA32_MCG_STATUS of each cpu have MCG_STATUS_RIPV bit set?
> MCG_STATUS is a per-thread MSR and will contain the status appropriate for that thread when #MC is delivered.
> So the RIPV bit will be set if, and only if, the thread saved a valid return address for this exception. The net result
> is that it is almost always set for "innocent bystander" CPUs that were dragged into the exception handler because
> of a broadcast #MC. We make the test because if it isn't set, then the do_machine_check() had better not return
> because we have no idea where it will return to - since there is not a valid return IP.
>

Got it, thanks for the details.

Regards,
Xunlei

      reply	other threads:[~2017-02-22  5:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23  8:01 Xunlei Pang
2017-01-23 12:51 ` Borislav Petkov
2017-01-23 13:35   ` Xunlei Pang
2017-01-23 14:50     ` Borislav Petkov
2017-01-23 17:40       ` Luck, Tony
2017-01-23 17:51         ` Borislav Petkov
2017-01-23 18:01           ` Luck, Tony
2017-01-23 18:14             ` Borislav Petkov
2017-01-24  2:33               ` Xunlei Pang
2017-01-24  1:46           ` Xunlei Pang
2017-01-24  1:51             ` Xunlei Pang
2017-01-24  1:27       ` Xunlei Pang
2017-01-24 12:22         ` Borislav Petkov
2017-01-26  6:30           ` Xunlei Pang
2017-01-26  6:44             ` Borislav Petkov
2017-02-16  5:36               ` Xunlei Pang
2017-02-16 10:18                 ` Borislav Petkov
2017-02-16 11:52                   ` Xunlei Pang
2017-02-16 12:22                     ` Borislav Petkov
2017-02-17  1:53                       ` Xunlei Pang
2017-02-17  9:07                         ` Borislav Petkov
2017-02-17 16:21                           ` Xunlei Pang
2017-02-21 18:20                             ` Luck, Tony
2017-02-22  5:50                               ` Xunlei Pang [this message]

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=58AD26B7.5070602@redhat.com \
    --to=xpang@redhat.com \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=k-ueda@ct.jp.nec.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=peterz@infradead.org \
    --cc=prarit@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=xlpang@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

Powered by JetHome