[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <571542D4.1030409@opensource.altera.com>
Date: Mon, 18 Apr 2016 15:25:56 -0500
From: Thor Thayer <tthayer@...nsource.altera.com>
To: Borislav Petkov <bp@...en8.de>
CC: Mauro Carvalho Chehab <m.chehab@...sung.com>,
Rob Herring <robh@...nel.org>, <dougthompson@...ssion.com>,
<pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<linux@....linux.org.uk>, <dinguyen@...nsource.altera.com>,
<grant.likely@...aro.org>, <devicetree@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <linux-edac@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <tthayer.linux@...il.com>
Subject: Re: [PATCH] Add EDAC peripheral init functions & Ethernet EDAC.
On 04/18/2016 03:06 PM, Borislav Petkov wrote:
> On Mon, Apr 18, 2016 at 10:02:27PM +0200, Borislav Petkov wrote:
>>> the number of uncorrectable errors is useful from a system point of
>>> view.
>
> I forgot: so altr_edac_a10_ecc_irq() panics on uncorrectable errors. Do we want
> to do that even for UEs coming from the network...?
>
> Seems a bit overboard to me...
>
Yes, as currently submitted, it is overboard and I'll fix this in the
next patch submission. In the uncorrectable error case, I plan to just
count the error. I'll add a constant flag in the Ethernet module's
edac_device_prv_data to determine if the panic should be bypassed.
Powered by blists - more mailing lists