linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] EDAC, ghes: Enable per-layer error reporting for ARM
Date: Thu, 19 Jul 2018 15:46:32 +0100	[thread overview]
Message-ID: <94e3a0fb-9b7d-045f-733b-9f063dcb39e4@arm.com> (raw)
In-Reply-To: <20180719140102.GB25185@nazgul.tnic>

Hi guys,

On 19/07/18 15:01, Borislav Petkov wrote:
> On Mon, Jul 16, 2018 at 01:26:49PM -0400, Tyler Baicar wrote:
>> Enable per-layer error reporting for ARM systems so that the error
>> counters are incremented per-DIMM.
>>
>> On ARM systems that use firmware first error handling it is understood

understood by whom? Is this written down somewhere, or is it the convention. (in
which case, lets get it written down somewhere)


>> that card=channel and module=DIMM on that channel. Populate that
I'm guessing this is the mapping between CPER records and the DMItable data.


>> information and enable per layer error reporting for ARM systems so that
>> the EDAC error counters are incremented based on DIMM number as per the
>> SMBIOS table rather than just incrementing the noinfo counters on the
>> memory controller.

Does this work on x86, and its just the dmi/cper fields have a subtle difference?


> I guess.
> 
> James?

I don't know anything about this stuff. Looks like the SMBIOS specification is
my new bedtime reading.



Thanks,

James

  reply	other threads:[~2018-07-19 14:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 17:26 [RFC PATCH] EDAC, ghes: Enable per-layer error reporting for ARM Tyler Baicar
2018-07-19 14:01 ` Borislav Petkov
2018-07-19 14:46   ` James Morse [this message]
2018-07-19 18:36     ` Tyler Baicar
2018-07-20  4:10       ` Borislav Petkov
2018-08-23  9:28       ` James Morse
2018-08-23 15:46         ` Tyler Baicar
2018-08-24  9:48           ` James Morse
2018-08-24 12:01             ` Borislav Petkov
2018-08-28 17:09               ` James Morse
2018-08-29  7:38                 ` Borislav Petkov
2018-08-29 10:20                   ` James Morse
2018-08-30 10:28                     ` Borislav Petkov
2018-08-24 14:30             ` wufan
2018-08-28 17:09               ` James Morse
2018-08-24 15:14             ` Tyler Baicar
2018-08-28 17:11               ` James Morse
2018-08-28 20:04                 ` Tyler Baicar

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=94e3a0fb-9b7d-045f-733b-9f063dcb39e4@arm.com \
    --to=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).