From: James Morse <james.morse@arm.com>
To: gengdongjiu <gengdongjiu@huawei.com>,
gengdongjiu <gengdj.1984@gmail.com>
Cc: robin.murphy@arm.com,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
xuqiang36@huawei.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Resend: How to handle the SMMU RAS Error in the kernel
Date: Fri, 30 Nov 2018 18:37:29 +0000 [thread overview]
Message-ID: <c769e2a5-f176-60fd-bcff-ef00e904736a@arm.com> (raw)
In-Reply-To: <7a93bf1b-7b7b-240e-bc74-68bf0ee18ac9@huawei.com>
Hi gengdongjiu,
On 21/11/2018 08:10, gengdongjiu wrote:
> On 2018/11/20 2:05, James Morse wrote:
>> On 17/11/2018 15:41, gengdongjiu wrote:
>>> In the current kernel, it only handles three kinds of error, which is
>>> memory error, PCIE device and ARM process. But now the SMMU already
>>> support the RAS, how to handle the SMMU RAS error in the kernel?
>>
>> What errors are being detected here?
>>
>> I don't know much about the SMMU, but I think we should start with a list of
>> errors that we want to handle.
>
> In our platform, the SMMU RAS error mainly include below which flow the SMMU spec:
> 1. one bit ECC error, reported as CE.
> 2. two bits ECC error, reported as UEU.
> 3. fetch error in the SMMUv3 spec, reported as UER.
These are faults, but this isn't enough information for software to act on.
Are these faults in the device, host-memory, or memory that is part of the SMMU?
Was the error discovered during a read/write by the device?, (which one?) Or the
SMMU's page-tables, or command-queue.
> The 2 and 3 should be handled, but I do not know how do recovery to it.
Me neither. If we can come up with the errors that can be detected, we can work
out which ones can be handled.
Thanks,
James
prev parent reply other threads:[~2018-11-30 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 15:41 gengdongjiu
2018-11-19 18:05 ` James Morse
2018-11-21 8:10 ` gengdongjiu
2018-11-30 18:37 ` James Morse [this message]
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=c769e2a5-f176-60fd-bcff-ef00e904736a@arm.com \
--to=james.morse@arm.com \
--cc=gengdj.1984@gmail.com \
--cc=gengdongjiu@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=xuqiang36@huawei.com \
/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®