mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Xie XiuQi <xiexiuqi@huawei.com>
Cc: tony.luck@intel.com, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org, chenwei68@huawei.com
Subject: Re: [PATCH v2] x86/mce: add support SRAO reported via CMC check
Date: Mon, 27 Nov 2017 11:19:26 +0100	[thread overview]
Message-ID: <20171127101926.7u5h5g6mfotwpfca@pd.tnic> (raw)
In-Reply-To: <1511575548-41992-1-git-send-email-xiexiuqi@huawei.com>

On Sat, Nov 25, 2017 at 10:05:48AM +0800, Xie XiuQi wrote:
> In Intel SDM Volume 3B (253669-063US, July 2017), SRAO could be
> reported either via MCE or CMC:
> 
>   In cases when SRAO is signaled via CMCI the error signature is
>   indicated via UC=1, PCC=0, S=0.
> 
>   Type(*1)	UC	EN	PCC	S	AR	Signaling
>   ---------------------------------------------------------------
>   UC		1	1	1	x	x	MCE
>   SRAR		1	1	0	1	1	MCE
>   SRAO		1	x(*2)	0	x(*2)	0	MCE/CMC
>   UCNA		1	x	0	0	0	CMC
>   CE		0	x	x	x	x	CMC
> 
>   NOTES:
>   1. SRAR, SRAO and UCNA errors are supported by the processor only
>      when IA32_MCG_CAP[24] (MCG_SER_P) is set.
>   2. EN=1, S=1 when signaled via MCE. EN=x, S=0 when signaled via CMC.
> 
> And there is a description in 15.6.2 UCR Error Reporting and Logging, for bit S:
> 
>   S (Signaling) flag, bit 56 - Indicates (when set) that a machine check
>   exception was generated for the UCR error reported in this MC bank...
>   When the S flag in the IA32_MCi_STATUS register is clear, this UCR error
>   was not signaled via a machine check exception and instead was reported
>   as a corrected machine check (CMC).
> 
> So we could merge this two case, and just remove the S=0 check for SRAO
> in mce_severity().
> 
> ---
> v2: add OVER=0 check and merge MCE and CMC case.
> 
> Signed-off-by: Xie XiuQi <xiexiuqi@huawei.com>
> Tested-by: Chen Wei <chenwei68@huawei.com>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
> ---
>  arch/x86/kernel/cpu/mcheck/mce-severity.c | 26 +++++++++++++++++---------
>  1 file changed, 17 insertions(+), 9 deletions(-)

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2017-11-27 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  2:05 Xie XiuQi
2017-11-27 10:19 ` Borislav Petkov [this message]
2017-12-04 19:43 ` [tip:ras/core] x86/MCE: Extend table to report action optional errors through CMCI too tip-bot for Xie XiuQi

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=20171127101926.7u5h5g6mfotwpfca@pd.tnic \
    --to=bp@alien8.de \
    --cc=chenwei68@huawei.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=xiexiuqi@huawei.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

all inboxes | Powered by JetHome®