From: Borislav Petkov <bp@alien8.de>
To: Tyler Baicar <tbaicar@codeaurora.org>
Cc: James Morse <james.morse@arm.com>,
harba@qti.qualcomm.com, mchehab@kernel.org,
linux-edac@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [RFC] EDAC, ghes: Enable per-layer error reporting for ARM
Date: Fri, 20 Jul 2018 06:10:05 +0200 [thread overview]
Message-ID: <20180720041005.GA25433@nazgul.tnic> (raw)
On Thu, Jul 19, 2018 at 02:36:21PM -0400, Tyler Baicar wrote:
> With the current ghes_edac setup, it seems the only way this could
> work would be to have the firmware always report the module value to
My experience with firmware so far is that it is a lost cause,
considering all the bugs, snafus and incompleteness it demonstrates...
> The other obvious but more messy way would be to have notifiers
> register to be called by ghes_edac and have a custom EDAC driver for
> each CPU to properly populate their layer information.
... which is what we do on x86 and whitelist only known-good platforms
in ghes_edac, which claim that their fw info is correct.
next reply other threads:[~2018-07-20 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 4:10 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-30 10:28 [RFC] EDAC, ghes: Enable per-layer error reporting for ARM Borislav Petkov
2018-08-29 10:20 James Morse
2018-08-29 7:38 Borislav Petkov
2018-08-28 20:04 Tyler Baicar
2018-08-28 17:11 James Morse
2018-08-28 17:09 James Morse
2018-08-28 17:09 James Morse
2018-08-24 15:14 Tyler Baicar
2018-08-24 14:30 wufan
2018-08-24 12:01 Borislav Petkov
2018-08-24 9:48 James Morse
2018-08-23 15:46 Tyler Baicar
2018-08-23 9:28 James Morse
2018-07-19 18:36 Tyler Baicar
2018-07-19 14:46 James Morse
2018-07-19 14:01 Borislav Petkov
2018-07-16 17:26 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=20180720041005.GA25433@nazgul.tnic \
--to=bp@alien8.de \
--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 \
/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).