[PATCH RFC v2] apei: Add ACPI APEI event notification support
lho at apm.com
Thu Nov 19 10:19:31 PST 2015
>> Top post - quick reply - you are correct. This is a vendor specific
>> implementation. APEI is generic, and in the general case there should
>> not be a need to do anything with a special driver. Some will need
>> their own special solution in the early days, but everyone else should
>> be able to go generic. In particular I expect those implementing EL3
>> to do firmware first handling and to signal the event independently of
>> any OS specific hooks.
> In the meantime, I got these two patches:
> which makes the GHES IRQ shared and, apparently solves the issue for
> I'd appreciate it if you guys took a look.
Let me explain a bit so that all of you understand what was changed
between version 2 and 3. For background, the issue is how to clear the
interrupt. In version 2, this is via the Linux kernel driver. In
version 3, we moved this to the FW and have the FW configures the GIC
directly to just mark the error interrupts (as spec in the GHES table)
pending. As it is pending only, it will get clear after the interrupt
gets processed. In doing this, two issues was observed. One is the
fact that we have multiple error cascades into a few interrupts. The
second issue is how ACPI upper layer handles return codes an function.
The patch in version 3 addresses both of these issues.
More information about the linux-arm-kernel