public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@akamai.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "tony.luck@intel.com" <tony.luck@intel.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"dougthompson@xmission.com" <dougthompson@xmission.com>,
	"m.chehab@samsung.com" <m.chehab@samsung.com>,
	"mitake@dcl.info.waseda.ac.jp" <mitake@dcl.info.waseda.ac.jp>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ie31200_edac: Add driver
Date: Wed, 09 Apr 2014 14:42:09 -0400	[thread overview]
Message-ID: <53459481.9020908@akamai.com> (raw)
In-Reply-To: <20140409113552.GJ6529@pd.tnic>

On 04/09/2014 07:35 AM, Borislav Petkov wrote:
> On Fri, Apr 04, 2014 at 09:14:04PM +0000, Jason Baron wrote:
>> Add 'ie31200_edac' driver for the E3-1200 series of Intel processors. Driver
>> is based on the following E3-1200 specs:
>>
>> http://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200-family-vol-2-datasheet.html
>> http://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200v3-vol-2-datasheet.html
>>
>> I've tested this on bad memory hardware, and observed correlating bad reads
>> and uncorrected memory errors as reported by the driver.
>>
>> Signed-off-by: Jason Baron <jbaron@akamai.com>
>> ---
>>  drivers/edac/Kconfig        |   7 +
>>  drivers/edac/Makefile       |   1 +
>>  drivers/edac/ie31200_edac.c | 540 ++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 548 insertions(+)
>>  create mode 100644 drivers/edac/ie31200_edac.c
>>
>> diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
>> index 878f090..27f44a1 100644
>> --- a/drivers/edac/Kconfig
>> +++ b/drivers/edac/Kconfig
>> @@ -186,6 +186,13 @@ config EDAC_I3200
>>  	  Support for error detection and correction on the Intel
>>  	  3200 and 3210 server chipsets.
>>  
>> +config EDAC_IE31200
>> +	tristate "Intel e312xx"
>> +	depends on EDAC_MM_EDAC && PCI && X86
>> +	help
>> +	  Support for error detection and correction on the Intel
>> +	  E3-1200 processor.
>> +
>>  config EDAC_X38
>>  	tristate "Intel X38"
>>  	depends on EDAC_MM_EDAC && PCI && X86
>> diff --git a/drivers/edac/Makefile b/drivers/edac/Makefile
>> index 4154ed6..c479a24 100644
>> --- a/drivers/edac/Makefile
>> +++ b/drivers/edac/Makefile
>> @@ -37,6 +37,7 @@ obj-$(CONFIG_EDAC_I82875P)		+= i82875p_edac.o
>>  obj-$(CONFIG_EDAC_I82975X)		+= i82975x_edac.o
>>  obj-$(CONFIG_EDAC_I3000)		+= i3000_edac.o
>>  obj-$(CONFIG_EDAC_I3200)		+= i3200_edac.o
>> +obj-$(CONFIG_EDAC_IE31200)		+= ie31200_edac.o
>>  obj-$(CONFIG_EDAC_X38)			+= x38_edac.o
>>  obj-$(CONFIG_EDAC_I82860)		+= i82860_edac.o
>>  obj-$(CONFIG_EDAC_R82600)		+= r82600_edac.o
>> diff --git a/drivers/edac/ie31200_edac.c b/drivers/edac/ie31200_edac.c
>> new file mode 100644
>> index 0000000..ae03d21
>> --- /dev/null
>> +++ b/drivers/edac/ie31200_edac.c
>> @@ -0,0 +1,540 @@
>> +/*
>> + * Intel E3-1200
>> + * Copyright (C) 2014 Jason Baron <jbaron@akamai.com>
>> + *
>> + * Support for the E3-1200 processor family. Heavily based on previous
>> + * Intel EDAC drivers.
> 
> Btw, remind me again why this isn't part of the sb_edac? AFAICT, the
> e3-12xx thing is a Sandybridge, right?
> 

So, I *think* that the E3-12xx processors cross microarchitectures.
So while E3-1270 is sandy bridge, the E3-1270 v3 is Haswell, and
the E3-1270 v2 is Ivy Bridge.

> Why not put it into sb_edac - it is small enough and if you're lucky,
> you might even share functionality?
> 

As far as I understand the sb_edac driver is decoding MCEs via a registration
function with the core MCE code.

However, we have a number of E3-12xx boxes, and we have not seen a MCE
generated on ue or ce errors.

Thanks,

-Jason





  parent reply	other threads:[~2014-04-09 18:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 21:13 [PATCH 0/3] Add new ie31200_edac driver Jason Baron
2014-04-04 21:13 ` [PATCH 1/3] readq/writeq: Add explicit lo_hi_[read|write]_q and hi_lo_[read|write]_q Jason Baron
2014-04-04 21:13 ` [PATCH 2/3] x38_edac: make use of lo_hi_readq() Jason Baron
2014-04-04 21:14 ` [PATCH 3/3] ie31200_edac: Add driver Jason Baron
2014-04-08  9:09   ` Borislav Petkov
2014-04-08 22:16     ` Jason Baron
2014-04-08 22:34       ` Luck, Tony
2014-04-09  3:03         ` Jason Baron
2014-04-09 11:11           ` Borislav Petkov
2014-04-09 11:13       ` Borislav Petkov
2014-04-09 11:35   ` Borislav Petkov
2014-04-09 13:34     ` Aristeu Rozanski
2014-04-09 17:17       ` Luck, Tony
2014-04-09 17:36         ` Borislav Petkov
2014-04-09 18:57           ` Jason Baron
2014-04-09 19:14             ` Borislav Petkov
2014-04-09 19:53               ` Jason Baron
2014-04-09 20:16                 ` Borislav Petkov
2014-04-09 21:33                   ` Luck, Tony
2014-04-09 22:15                     ` Jason Baron
2014-04-09 22:44                       ` Luck, Tony
2014-04-10  1:52                         ` Jason Baron
2014-04-10  9:30                         ` Borislav Petkov
2014-06-11 21:54                     ` Jason Baron
2014-04-09 18:42     ` Jason Baron [this message]
2014-04-07 20:00 ` [PATCH 0/3] Add new ie31200_edac driver Borislav Petkov

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=53459481.9020908@akamai.com \
    --to=jbaron@akamai.com \
    --cc=bp@alien8.de \
    --cc=dougthompson@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mingo@kernel.org \
    --cc=mitake@dcl.info.waseda.ac.jp \
    --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