From: gengdongjiu <gengdongjiu@huawei.com>
To: Shiju Jose <shiju.jose@huawei.com>, <xuwei5@hisilicon.com>
Cc: <arnd@arndb.de>, <james.morse@arm.com>, <tbaicar@codeaurora.org>,
<xiexiuqi@huawei.com>, <zhengqiang10@huawei.com>,
<linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH]arm64:defconfig:enable ACPI_APEI_SEA
Date: Wed, 21 Mar 2018 09:48:37 +0800 [thread overview]
Message-ID: <a56d6415-0755-6125-84c3-f5aef95434ca@huawei.com> (raw)
In-Reply-To: <aa732187-e12a-68e5-d15e-84090855d2c5@huawei.com>
Hi Shiju,
The configuration "CONFIG_ACPI_APEI_SEA" is needed to manually enable?
In the "drivers/acpi/apei/Kconfig" file, the default value of ACPI_APEI_SEA is "y"
config ACPI_APEI_SEA
bool "APEI Synchronous External Abort logging/recovering support"
depends on ARM64 && ACPI_APEI_GHES
default y
help
This option should be enabled if the system supports
firmware first handling of SEA (Synchronous External Abort).
SEA happens with certain faults of data abort or instruction
abort synchronous exceptions on ARMv8 systems. If a system
supports firmware first handling of SEA, the platform analyzes
and handles hardware error notifications from SEA, and it may then
form a HW error record for the OS to parse and handle. This
option allows the OS to look for such hardware error record, and
take appropriate action.
On 2018/3/20 20:23, Shiju Jose wrote:
> Enable ACPI APEI SEA option for arm64, to handle
> ARMv8 SEA(Synchronous External Abort).
>
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
> Cc: Tyler Baicar <tbaicar@codeaurora.org>
> Cc: James Morse <james.morse@arm.com>
> Cc: Dongjiu Geng <gengdongjiu@huawei.com>
> Cc: Xie XiuQi <xiexiuqi@huawei.com>
> Cc: Qiang Zheng <zhengqiang10@huawei.com>
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 634b373..5ddf25c 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -574,6 +574,7 @@ CONFIG_ACPI_APEI_GHES=y
> CONFIG_ACPI_APEI_PCIEAER=y
> CONFIG_ACPI_APEI_MEMORY_FAILURE=y
> CONFIG_ACPI_APEI_EINJ=y
> +CONFIG_ACPI_APEI_SEA=y
> CONFIG_EXT2_FS=y
> CONFIG_EXT3_FS=y
> CONFIG_EXT4_FS_POSIX_ACL=y
>
next prev parent reply other threads:[~2018-03-21 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 12:23 Shiju Jose
2018-03-21 1:48 ` gengdongjiu [this message]
2018-03-21 10:50 ` Shiju Jose
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=a56d6415-0755-6125-84c3-f5aef95434ca@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=arnd@arndb.de \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=xiexiuqi@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=zhengqiang10@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®