From: Chen Gong <gong.chen@linux.intel.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@suse.de>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: [PATCH] x86/mce: Pay no attention to 'F' bit in MCACOD when parsing 'UC' errors.
Date: Wed, 24 Jul 2013 02:16:26 -0400 [thread overview]
Message-ID: <20130724061626.GA18995@gchen.bj.intel.com> (raw)
In-Reply-To: <CA+8MBbLkWZKwG40XMXCV75Vr=6pKq9rijRamt7=qALhc72SCTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
On Tue, Jul 23, 2013 at 03:51:14PM -0700, Tony Luck wrote:
> Date: Tue, 23 Jul 2013 15:51:14 -0700
> From: Tony Luck <tony.luck@gmail.com>
> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Cc: Borislav Petkov <bp@suse.de>, Chen Gong <gong.chen@linux.intel.com>,
> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
> Subject: Re: [PATCH] x86/mce: Pay no attention to 'F' bit in MCACOD when
> parsing 'UC' errors.
>
> Gah ... there is another bug in that unaffected thread entry. The check for
> MCG_STATUS should be for RIPV=1 *and* EIPV=0
>
I set "MCGMASK(MCG_STATUS_RIPV, MCG_STATUS_RIPV)" becase
I want it to cover Non-Affected Logical Processors (1,0)
and Affected Logical Processor/Recoverable continuable (1,1).
I think both of them are continuable so they should be as
*KEEP*.
> gmail will mess this patch up ... but should still be readable.
>
> -Tony
>
> ---
>
> diff --git a/arch/x86/kernel/cpu/mcheck/mce-severity.c
> b/arch/x86/kernel/cpu/mcheck/mce-severity
> index 7f6ab4e..48f0fd2 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce-severity.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce-severity.c
> @@ -112,7 +112,7 @@ static struct severity {
> MCESEV(
> KEEP, "Action required but unaffected thread is continuable",
> SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR,
> MCI_UC_SAR|MCI_ADDR),
> - MCGMASK(MCG_STATUS_RIPV, MCG_STATUS_RIPV)
> + MCGMASK(MCG_STATUS_RIPV|MCG_STATUS_EIPV, MCG_STATUS_RIPV)
> ),
> MCESEV(
> AR, "Action required: data load error in a user process",
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-24 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 20:34 [PATCH] x86/mce: Pay no attention to 'F' bit in MCACOD when parsing 'UC' errors Luck, Tony
2013-07-23 22:51 ` Tony Luck
2013-07-24 6:16 ` Chen Gong [this message]
2013-07-25 10:38 ` Naveen N. Rao
2013-07-25 18:01 ` Luck, Tony
2013-07-31 10:06 ` Naveen N. Rao
2013-07-24 6:19 ` Chen Gong
2013-07-24 15:55 ` Naveen N. Rao
2013-07-24 17:00 ` Luck, Tony
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=20130724061626.GA18995@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=tony.luck@gmail.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