From: Lv Ying <lvying6@huawei.com>
To: <rafael@kernel.org>, <lenb@kernel.org>, <james.morse@arm.com>,
<tony.luck@intel.com>, <bp@alien8.de>, <naoya.horiguchi@nec.com>,
<linmiaohe@huawei.com>, <akpm@linux-foundation.org>,
<xueshuai@linux.alibaba.com>, <ashish.kalra@amd.com>
Cc: <xiezhipeng1@huawei.com>, <wangkefeng.wang@huawei.com>,
<xiexiuqi@huawei.com>, <tanxiaofei@huawei.com>,
<cuibixuan@linux.alibaba.com>, <lvying6@huawei.com>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: [RFC PATCH v2 0/1] ACPI: APEI: Make synchronization errors call
Date: Fri, 9 Dec 2022 17:54:06 +0800 [thread overview]
Message-ID: <20221209095407.383211-1-lvying6@huawei.com> (raw)
RFC PATCH v2 -> RFC PATCH v1 CHANGE:
====================================
1. based on Shuai and XiuQi's suggestion, this patchset just
consider SEA notification is synchronous error in APEI NMI-like
notification(NMI, SEA, SDEI)[1][2]
2. based on Bixuan's suggestion[3], based on the work of RFC PATCH v1 first
patch, the problem described in RFC PATCH V1 second patch commit message no
longer exists. Integrate the second patch into the first patch.[2]
[1] https://lore.kernel.org/lkml/5afef5fd-7e44-32ae-fa94-5fcf47d4b4df@linux.alibaba.com/
[2] https://lore.kernel.org/lkml/6c9a17ad-fe68-bbb5-bb37-edbcfbbc2fee@huawei.com/
[3] https://lore.kernel.org/lkml/ddc81946-8b76-ea49-ebf5-f2de2e30540d@linux.alibaba.com/
Lv Ying (1):
ACPI: APEI: Make memory_failure() triggered by synchronization errors
execute in the current context
drivers/acpi/apei/ghes.c | 20 +++++++++-------
mm/memory-failure.c | 50 +++++++++++++++++++++++++++++-----------
2 files changed, 48 insertions(+), 22 deletions(-)
--
2.36.1
next reply other threads:[~2022-12-09 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 9:54 Lv Ying [this message]
2022-12-09 9:54 ` [RFC PATCH v2 1/1] ACPI: APEI: Make memory_failure() triggered by synchronization errors execute in the current context Lv Ying
2022-12-15 0:26 ` HORIGUCHI NAOYA(堀口 直也)
2022-12-15 2:45 ` Lv Ying
2022-12-15 4:45 ` Shuai Xue
2022-12-16 12:23 ` Lv Ying
2022-12-21 11:15 ` 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=20221209095407.383211-1-lvying6@huawei.com \
--to=lvying6@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=cuibixuan@linux.alibaba.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=rafael@kernel.org \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=xiexiuqi@huawei.com \
--cc=xiezhipeng1@huawei.com \
--cc=xueshuai@linux.alibaba.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