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 23:10:52 +0200 [thread overview]
Message-ID: <20130626211052.GN20274@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31C56603@ORSMSX106.amr.corp.intel.com>
On Wed, Jun 26, 2013 at 09:00:10PM +0000, Luck, Tony wrote:
> > And this obviously is the case for the hardware too, I assume, not only
> > the SDM?
>
> Yes - we have a magic process which reconfigures all deployed silicon whenever
> a new SDM is published :-)
Haha, I wouldn't wonder if your silicon dudes come up with
reprogrammable fuses someday :-)
> Actually the SDM had been collecting new features for each generation ... each
> time just bolting on a new paragraph or table. I snapped when I saw the table
> that was proposed for 15-20 to add "continuable" errors and complained that
> it had gotten way too complicated ... and proposed the version that you see in
> the current SDM.
>
> It accurately portrays what older generations implemented, and adds the new
> continuable (EIPV=1, RIPV=1) while removing many rows and columns.
Cool :)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-06-26 21:10 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
2013-06-26 21:00 ` Luck, Tony
2013-06-26 21:10 ` Borislav Petkov [this message]
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=20130626211052.GN20274@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®