[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171219104500.5otagp7m7dqretd2@lakrids.cambridge.arm.com>
Date: Tue, 19 Dec 2017 10:45:00 +0000
From: Mark Rutland <mark.rutland@....com>
To: Bharat Kumar Gogada <bharatku@...inx.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
Will Deacon <Will.Deacon@....com>,
"james.morse@....com" <james.morse@....com>,
"julien.thierry@....com" <julien.thierry@....com>,
"punit.agrawal@....com" <punit.agrawal@....com>,
"tbaicar@...eaurora.org" <tbaicar@...eaurora.org>,
"mingo@...nel.org" <mingo@...nel.org>
Subject: Re: Linux Kernel handling AXI DECERR/SLVERR
On Tue, Dec 19, 2017 at 10:23:25AM +0000, Bharat Kumar Gogada wrote:
> Hi All,
Hi,
> When Linux is booted on ARM64 platform and an access to peripheral returns
> DECERR or SLVERR on AXI.
>
> In the above error cases how would Linux kernel handle these faults ? Will it
> hang/recover ?
I believe that on contemporary CPUs these will result in an SError. As
SErrors are asynchronous, and (in the absence of RAS extensions) their
cause cannot be determined, these are treated as fatal, and the kernel
will panic().
Thanks,
Mark.
Powered by blists - more mailing lists