From: Jason Baron <jbaron@akamai.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Aristeu Rozanski <aris@redhat.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:57:19 -0400 [thread overview]
Message-ID: <5345980F.7070604@akamai.com> (raw)
In-Reply-To: <20140409173633.GN6529@pd.tnic>
On 04/09/2014 01:36 PM, Borislav Petkov wrote:
> On Wed, Apr 09, 2014 at 05:17:53PM +0000, Luck, Tony wrote:
>> The E3-12xx processors connect out to a different (desktop) chipset
>> from the E5 (server parts). Perhaps that means the memory controller
>> are different too???
>
> You gotta love how Intel has a different memory controller for server
> and desktop parts. :-)
>
Right, so maybe the fact that its a desktop chipset means that it behaves
differently and doesn't raise MCEs on memory errors. We have a bunch
of these processors and we haven't yet seen an MCE raised on a memory
error.
> Btw, is that the official memory controller name you'd like the edac
> driver to be called - ie31200? I'm asking because it should probably
> have a name which denotes the memory controller and not the processor
> series... (who knows, we might find that memory controller built in
> somewhere else :-))
>
> Thanks.
>
The reason I went with ie31200 is that afaiu the memory controller
hub is integrated into the cpu. Another alternative might be ie312xx?
Thanks,
-Jason
next prev parent reply other threads:[~2014-04-09 18:57 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 [this message]
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
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=5345980F.7070604@akamai.com \
--to=jbaron@akamai.com \
--cc=aris@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.