From: Borislav Petkov <bp@alien8.de>
To: James Morse <james.morse@arm.com>
Cc: Tyler Baicar <baicar.tyler@gmail.com>,
Tyler Baicar <tbaicar@codeaurora.org>,
wufan@codeaurora.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
harba@qti.qualcomm.com, mchehab@kernel.org,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
linux-edac@vger.kernel.org
Subject: Re: [RFC PATCH] EDAC, ghes: Enable per-layer error reporting for ARM
Date: Thu, 30 Aug 2018 12:28:15 +0200 [thread overview]
Message-ID: <20180830102815.GB20005@nazgul.tnic> (raw)
In-Reply-To: <2e7b984a-8f8f-dad7-4ee5-043dd236a9b1@arm.com>
On Wed, Aug 29, 2018 at 11:20:48AM +0100, James Morse wrote:
> Right. I'd like ghes-edac to work in the same way for both architectures.
>
> I think this is best done by stuffing the dmi-handle in struct dimm_info during
> ghes_edac_dmidecode(), then populating the struct edac_raw_error_desc layers
> from the matching mci->dimms 'location'.
>
> For EDAC_MC_LAYER_ALL_MEM this boils down to a flat index, so pointer arithmetic
> on mci->dimms is an appropriate short cut.
It all sounds nice on paper but you should try it on a couple of
machines first. See whether/how it actually works there.
Also, this probably would need to not change x86 unless you wanna fix it
there too. I'd think twice before I attempt such a thing though :)
> (We should probably 'FIXME: It shouldn't be hard to also fill the DIMM labels'
> at the same time so that no-one is tempted to interpret the edac:dimm-idx)
See above.
> > In an ideal world, I'd like to be able to query the SPD chips on the
>
> (oh, that can be done?)
There was some talk initially and I've seen BIOS read SPD chips and
showing DIMM info but I've heard the word "proprietary" a couple of
times. Haven't dug any deeper though.
> I got educated by the people who look after specifications last time I touched
> this [0]. SMBIOS tables are required by Arm's 'Server Base Boot Requirements',
> It lists the memory-device and physical-memory-array as required.
It is always better to have certification on your side. Should make ARM
vendors dance.
> I will drop them a note that we will be depending on the handle, and it should
> go on the list too... if its not populated on today's systems we can fall back
> to !e->enable_per_layer_report as we do today.
Right.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2018-08-30 10:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 17:26 Tyler Baicar
2018-07-19 14:01 ` Borislav Petkov
2018-07-19 14:46 ` James Morse
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 [this message]
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=20180830102815.GB20005@nazgul.tnic \
--to=bp@alien8.de \
--cc=baicar.tyler@gmail.com \
--cc=harba@qti.qualcomm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tbaicar@codeaurora.org \
--cc=wufan@codeaurora.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
all inboxes | Powered by JetHome®