[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221205160043.57465-1-xiexiuqi@huawei.com>
Date: Tue, 6 Dec 2022 00:00:39 +0800
From: Xie XiuQi <xiexiuqi@...wei.com>
To: <catalin.marinas@....com>, <will@...nel.org>,
<james.morse@....com>, <rafael@...nel.org>, <tony.luck@...el.com>,
<robert.moore@...el.com>, <bp@...en8.de>, <devel@...ica.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-acpi@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: <tanxiaofei@...wei.com>, <wangxiongfeng2@...wei.com>,
<lvying6@...wei.com>, <naoya.horiguchi@....com>,
<wangkefeng.wang@...wei.com>
Subject: [PATCH v3 0/4] arm64: improve handle synchronous External Data Abort
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
Powered by blists - more mailing lists