From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chen Gong <gong.chen@linux.intel.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: [PATCH] x86/mce: Update MCE severity condition check
Date: Wed, 26 Jun 2013 22:36:39 +0200 [thread overview]
Message-ID: <20130626203639.GM20274@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31C5653E@ORSMSX106.amr.corp.intel.com>
On Wed, Jun 26, 2013 at 08:23:47PM +0000, Luck, Tony wrote:
> MCESEV(
> > - KEEP, "HT thread notices Action required: data load error",
> > - SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR|MCACOD, MCI_UC_SAR|MCI_ADDR|MCACOD_DATA),
> > - MCGMASK(MCG_STATUS_EIPV, 0)
> > + KEEP, "Action required but unaffected thread is continuable",
> > + SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR|MCACOD, MCI_UC_SAR|MCI_ADDR),
>
> > Why did we lose MCACOD_DATA from the MASK above? Was this intentional?
>
>
> We used to have separate entries for "HT thread notices ... data load" and "HT thread notices ... instruction load"
> because the old SDM had a complex table calling out the bit settings for each type of recoverable machine check.
>
> Latest SDM simplifies the table making it clear that for every SRAR (software recoverable action required) error
> we'll have the same bits in MCG_STATUS (EIPV=0, RIPV=1) ... so we don't need to check for the MCACOD value.
> See attached snapshot of the new table.
And this obviously is the case for the hardware too, I assume, not only
the SDM?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-06-26 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 9:16 [PATCH] x86/MCE: " Chen Gong
2013-06-20 9:41 ` Borislav Petkov
2013-06-21 12:38 ` Chen Gong
2013-06-25 6:32 ` Naveen N. Rao
2013-06-25 16:31 ` Luck, Tony
2013-06-25 20:08 ` Naveen N. Rao
2013-06-26 9:18 ` Chen Gong
[not found] ` <0134840@agluck-desk.sc.intel.com>
2013-06-26 19:08 ` [PATCH] x86/mce: " Borislav Petkov
2013-06-26 20:23 ` Luck, Tony
2013-06-26 20:36 ` Borislav Petkov [this message]
2013-06-26 21:00 ` Luck, Tony
2013-06-26 21:10 ` Borislav Petkov
2013-06-27 6:42 ` Chen Gong
2013-06-27 8:55 ` Naveen N. Rao
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=20130626203639.GM20274@pd.tnic \
--to=bp@alien8.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--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
all inboxes | Powered by JetHome®