[PATCH] ghes_edac: enable HIP08 platform edac driver

From
James Morse <james.morse@arm.com>
Date
2018-05-14 15:12:08
Also in
linux-edac
Hi Borislav,

(CC: +linux-arm list, just in case there is wider discussion)

On 14/05/18 10:47, Borislav Petkov wrote:
On Mon, May 14, 2018 at 12:11:28PM +0800, Zhengqiang wrote:
quoted
In ARM64 defconfig, ghes_edac is default load. memory error report to
user space rasdaemon tool through function ghes_edac_report_mem_error,
we need it.
So depending on whether there will be an ARM64 edac driver, we can do
I'm afraid there could be a mix: The v8.2 CPU RAS Extensions mean the kernel can
do kernel first. (I agree for those systems there should only be one edac driver).
For systems without the v8.2 CPU RAS Extensions firmware-first is the only way
of doing it.

the platform whitelisting on x86 only if ARM prefers to do the reporting
through ghes_edac. James?
I'm afraid I'd like to keep both doors open. Kernel-first handling will require
some ACPI-table/DT property as some aspects of the CPU extensions aren't
discover-able. Can't we use this to pick up whether the platform supports
firmware-first (HEST and GHES entries) or kernel-first via some as-yet-undefined
HEST bits?

Without GHES entries this code would never be run. So we 'just' need to catch
systems that are describing both. (which can be the platform specific kernel
first bits problem to do)


Thanks,

James
Thread (14 messages) 14 messages, 4 authors, last reply 2018-05-22
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help