mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: gong.chen@linux.intel.com, tony.luck@intel.com
Cc: bp@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mce: Pay no attention to 'F' bit in MCACOD when parsing 'UC' errors.
Date: Thu, 25 Jul 2013 16:08:26 +0530	[thread overview]
Message-ID: <20130725103647.5009.92648.stgit@localhost.localdomain> (raw)
In-Reply-To: <20130724061626.GA18995@gchen.bj.intel.com>

On 07/24/2013 11:46 AM, Chen Gong wrote:
> 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*.

For affected logical processors, we won't be able to continue if we were in
kernel-space. Right? So, it looks like we should panic and I think this gets
covered by "Action required: unknown MCACOD" entry later on, though a more
explicit entry might help. For user-space, the next two entries cover AR.

Does the below help or am I reading this wrong?

Thanks,
Naveen

--
We have three categories under MCA Action Required (AR):
1. Unaffected threads/cpu (RIPV=1,EIPV=0): always continuable
2. Affected threads (RIPV=EIPV=1): continuable
3. Affected threads (RIPV=0): not continuable

The consolidated entry (Tony's new patch) should only cover (1).

(2) and (3) are covered for user-space by the two entries following the entry
for (1) for data load and instruction fetch errors.

(3) is covered for kernel-space by the earlier entry for "In kernel and no
restart IP" where we panic. The below patch is to make (2) explicit for
kernel-space.


Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
---
 arch/x86/kernel/cpu/mcheck/mce-severity.c |    6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/arch/x86/kernel/cpu/mcheck/mce-severity.c b/arch/x86/kernel/cpu/mcheck/mce-severity.c
index e2703520..585ddbb 100644
--- a/arch/x86/kernel/cpu/mcheck/mce-severity.c
+++ b/arch/x86/kernel/cpu/mcheck/mce-severity.c
@@ -115,6 +115,12 @@ static struct severity {
 		MCGMASK(MCG_STATUS_RIPV, MCG_STATUS_RIPV)
 		),
 	MCESEV(
+		PANIC, "Action required but kernel thread is not continuable",
+		SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR, MCI_UC_SAR|MCI_ADDR),
+		MCGMASK(MCG_STATUS_RIPV|MCG_STATUS_EIPV, MCG_STATUS_RIPV|MCG_STATUS_EIPV),
+		KERNEL
+		),
+	MCESEV(
 		AR, "Action required: data load error in a user process",
 		SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR|MCACOD, MCI_UC_SAR|MCI_ADDR|MCACOD_DATA),
 		USER


  reply	other threads:[~2013-07-25 10:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 20:34 Luck, Tony
2013-07-23 22:51 ` Tony Luck
2013-07-24  6:16   ` Chen Gong
2013-07-25 10:38     ` Naveen N. Rao [this message]
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=20130725103647.5009.92648.stgit@localhost.localdomain \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=bp@suse.de \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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