From: Arnd Bergmann <arnd@arndb.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Jon Masters <jcm@redhat.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
"patches@apm.com" <patches@apm.com>,
Rob Herring <robh+dt@kernel.org>, Loc Ho <lho@apm.com>,
Doug Thompson <dougthompson@xmission.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH 2/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver
Date: Mon, 01 Jun 2015 20:37:39 +0200 [thread overview]
Message-ID: <2884982.Ci49nmtWmA@wuerfel> (raw)
In-Reply-To: <20150601183114.GE10169@pd.tnic>
On Monday 01 June 2015 20:31:14 Borislav Petkov wrote:
> On Mon, Jun 01, 2015 at 10:46:55AM -0700, Loc Ho wrote:
> > You are right... Let me just prints the error code instead. Anyone who
> > care will have to do post processing.
>
> Don't forget about the usability of the driver. If a user has to go
> open manuals when an error happens, you could just as well report naked
> register values and have a tool decode them.
>
> And this strategy (mcelog) turned out to be a real PITA, IMO.
>
> > Future or existent next generation may re-define them.
>
> You could easily have a strings array of per-family or per-soc error
> descriptions. For an example, take a look at drivers/edac/mce_amd.c
> which decodes MCEs on all relevant AMD machines. This is much more
> user-friendly than dumping register values which most people have no
> idea of where to start looking (and they don't really need to).
That would require having a way to identify the SoC with a distinct
compatible string. I don't know if a name exists for X-Gene that could
be used here.
Arnd
next prev parent reply other threads:[~2015-06-01 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 22:04 [PATCH 0/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Loc Ho
[not found] ` <1432937075-16558-1-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-05-29 22:04 ` [PATCH 1/3] Documentation: Update the APM X-Gene SoC EDAC DTS binding for L3/SoC subnodes Loc Ho
[not found] ` <1432937075-16558-2-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-05-29 22:04 ` [PATCH 2/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Loc Ho
[not found] ` <1432937075-16558-3-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-05-29 22:04 ` [PATCH 3/3] arm64: Add L3/SoC DT subnodes to the APM X-Gene SoC EDAC node Loc Ho
2015-06-01 11:43 ` [PATCH 2/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Borislav Petkov
[not found] ` <20150601114346.GA10169-fF5Pk5pvG8Y@public.gmane.org>
2015-06-01 17:26 ` Loc Ho
2015-06-01 14:39 ` Arnd Bergmann
2015-06-01 17:46 ` Loc Ho
[not found] ` <CAPw-ZTm+1hfh4b-opq=HQDek-wc4A4nT=B6DcuyUBWsm8a-ZbQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-01 18:31 ` Borislav Petkov
2015-06-01 18:37 ` Arnd Bergmann [this message]
2015-06-01 18:59 ` Loc Ho
2015-06-01 14:39 ` [PATCH 1/3] Documentation: Update the APM X-Gene SoC EDAC DTS binding for L3/SoC subnodes Arnd Bergmann
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=2884982.Ci49nmtWmA@wuerfel \
--to=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=dougthompson@xmission.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jcm@redhat.com \
--cc=lho@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=patches@apm.com \
--cc=robh+dt@kernel.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