From: Xie XiuQi <xiexiuqi@huawei.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
<james.morse@arm.com>, <rafael@kernel.org>, <tony.luck@intel.com>,
<robert.moore@intel.com>, <bp@alien8.de>, <devel@acpica.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <tanxiaofei@huawei.com>, <wangxiongfeng2@huawei.com>,
<lvying6@huawei.com>, <naoya.horiguchi@nec.com>,
<wangkefeng.wang@huawei.com>
Subject: [PATCH v3 0/4] arm64: improve handle synchronous External Data Abort
Date: Tue, 6 Dec 2022 00:00:39 +0800 [thread overview]
Message-ID: <20221205160043.57465-1-xiexiuqi@huawei.com> (raw)
This series fix some issue for arm64 synchronous External Data Abort.
1. fix unhandled processor error
According to the RAS documentation, if we cannot determine the impact
of the error based on the details of the error when an SEA occurs, the
process cannot safely continue to run. Therefore, for unhandled error,
we should signal the system and terminate the process immediately.
2. improve for handling memory errors
If error happened in current execution context, we need pass
MF_ACTION_REQUIRED flag to memory_failure(), and if memory_failure()
recovery failed, we must handle this case, other than ignore it.
---
v3: add improve for handing memory errors
v2: fix compile warning reported by kernel test robot.
Xie XiuQi (4):
ACPI: APEI: include missing acpi/apei.h
arm64: ghes: fix error unhandling in synchronous External Data Abort
arm64: ghes: handle the case when memory_failure recovery failed
arm64: ghes: pass MF_ACTION_REQUIRED to memory_failure when sea
arch/arm64/kernel/acpi.c | 6 ++++++
drivers/acpi/apei/apei-base.c | 5 +++++
drivers/acpi/apei/ghes.c | 31 ++++++++++++++++++++++++-------
include/acpi/apei.h | 1 +
include/linux/mm.h | 2 +-
mm/memory-failure.c | 24 +++++++++++++++++-------
6 files changed, 54 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2022-12-05 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 16:00 Xie XiuQi [this message]
2022-12-05 16:00 ` [PATCH v3 1/4] ACPI: APEI: include missing acpi/apei.h Xie XiuQi
2022-12-05 16:00 ` [PATCH v3 2/4] arm64: ghes: fix error unhandling in synchronous External Data Abort Xie XiuQi
2022-12-05 16:00 ` [PATCH v3 3/4] arm64: ghes: handle the case when memory_failure recovery failed Xie XiuQi
2022-12-05 16:00 ` [PATCH v3 4/4] arm64: ghes: pass MF_ACTION_REQUIRED to memory_failure when sea Xie XiuQi
2022-12-10 13:35 ` [PATCH v3 0/4] arm64: improve handle synchronous External Data Abort Shuai Xue
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=20221205160043.57465-1-xiexiuqi@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=devel@acpica.org \
--cc=james.morse@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvying6@huawei.com \
--cc=naoya.horiguchi@nec.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=wangxiongfeng2@huawei.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).