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: Wed, 29 Aug 2018 09:38:04 +0200 [thread overview]
Message-ID: <20180829073804.GA6843@nazgul.tnic> (raw)
In-Reply-To: <0a94db2a-2569-ac46-1a79-a05f46a4ea6f@arm.com>
On Tue, Aug 28, 2018 at 06:09:24PM +0100, James Morse wrote:
> Does x86 have another source of memory-topology information it needs to
> correlate smbios with?
Bah, pinpointing the DIMM on x86 is a mess. There's no reliable way to
say which DIMM it is in certain cases (interleaving, mirrorring, ...)
and it is all platform-dependent. So we do the layers to dump a memory
location (node, memory controller, ....) so that we can at least limit
the number of DIMMs the user needs to replace/try.
In an ideal world, I'd like to be able to query the SPD chips on the
DIMMs and build the topology and then when an error happens to say,
"error in DIMM <silkscreen>" where silkscreen is what is written on the
motherboard under the DIMM socket.
But I don't see that happening any time soon...
> For arm there is nothing else describing the memory-topology, so as long as we
> can correlate the smbios table and ghes:cper records through the handles, we can
> get this working for all systems.
And then make sure vendors fill in the proper info in smbios. Because that's
also a mess on x86.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2018-08-29 7:40 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 [this message]
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=20180829073804.GA6843@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®