From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] acpi, apei, arm64: APEI initial support for aarch64.
Date: Tue, 08 Dec 2015 20:52:28 +0800 [thread overview]
Message-ID: <5666D28C.4090305@linaro.org> (raw)
In-Reply-To: <20151208123433.GB404@red-moon>
Hi Lorenzo,
On 12/08/2015 08:34 PM, Lorenzo Pieralisi wrote:
> On Tue, Dec 08, 2015 at 03:03:03PM +0800, fu.wei at linaro.org wrote:
>> From: Tomasz Nowicki <tomasz.nowicki@linaro.org>
>
> [...]
>
>> +#if defined(__i386__) || defined(__x86_64__)
>> /*
>> * Check if firmware advertises firmware first mode. We need FF bit to be set
>> * along with a set of MC banks which work in FF mode.
>> */
>> static int __init hest_parse_cmc(struct acpi_hest_header *hest_hdr, void *data)
>> {
>> - return arch_apei_enable_cmcff(hest_hdr, data);
>> + if (!acpi_disable_cmcff)
>
> Why do not you define the flag above in this file (move it out of x86 -
> that's what I was aiming at in my previous reply) and remove this ifdeffery
> altogether (First firmware handling could apply to arm64 too according to
> specs and ACPI on arm64 guidelines) ?
If I understand it correctly, CMC (Corrected Machine Check) is for IA32
only, see section 18.3.2.1 IA-32 Architecture Machine Check Exception
in ACPI 6.0. for ARM64, we can use other type of error source for
firmware first handling, such as Generic Hardware Error Source, did
I miss something?
Thanks
Hanjun
next prev parent reply other threads:[~2015-12-08 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 7:03 [PATCH v4] acpi, apei, arm64: APEI initial support for aarch64 fu.wei at linaro.org
2015-12-08 11:26 ` Hanjun Guo
2015-12-08 12:45 ` Fu Wei
2015-12-08 12:34 ` Lorenzo Pieralisi
2015-12-08 12:52 ` Hanjun Guo [this message]
2015-12-08 13:08 ` Fu Wei
2015-12-08 14:07 ` Lorenzo Pieralisi
2015-12-09 3:25 ` Fu Wei
2015-12-10 2:02 ` Fu Wei
2015-12-10 11:01 ` Will Deacon
2015-12-14 11:20 ` Borislav Petkov
2015-12-14 11:46 ` Will Deacon
2015-12-14 12:39 ` Borislav Petkov
2015-12-08 15:53 ` Suzuki K. Poulose
2015-12-09 3:00 ` Fu Wei
2015-12-14 10:46 ` Borislav Petkov
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=5666D28C.4090305@linaro.org \
--to=hanjun.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).