[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180416215903.7318-1-mr.nuke.me@gmail.com>
Date: Mon, 16 Apr 2018 16:58:59 -0500
From: Alexandru Gagniuc <mr.nuke.me@...il.com>
To: linux-acpi@...r.kernel.org, linux-edac@...r.kernel.org
Cc: rjw@...ysocki.net, lenb@...nel.org, tony.luck@...el.com,
bp@...en8.de, tbaicar@...eaurora.org, will.deacon@....com,
james.morse@....com, shiju.jose@...wei.com, zjzhang@...eaurora.org,
gengdongjiu@...wei.com, linux-kernel@...r.kernel.org,
alex_gagniuc@...lteam.com, austin_bolen@...l.com,
shyam_iyer@...l.com, devel@...ica.org, mchehab@...nel.org,
robert.moore@...el.com, erik.schmauss@...el.com,
Alexandru Gagniuc <mr.nuke.me@...il.com>
Subject: [RFC PATCH v2 0/4] acpi: apei: Improve error handling with firmware-first
Or "acpi: apei: Don't let puny firmware crash us with puny errors"
This is the improved implementation following feedback from James Morse
(thanks James!). This implementation, I think, is more modular, and easier to
follow, and just makes more sense.
I'm leaving this as RFC because the BIOS team is a bit scared of an OS
that won't crash when it's told to. However, if people like the idea, then
I have nothing against merging this.
Changes since v1:
- Due to popular request, the panic() is left in the NMI handler
- GHES AER handler is split into NMI and non-NMI portions
- ghes_notify_nmi() does not panic on deferrable errors
- The handlers are put in a mapping and given a common call signature
Alexandru Gagniuc (4):
EDAC, GHES: Remove unused argument to ghes_edac_report_mem_error
acpi: apei: Split GHES handlers outside of ghes_do_proc
acpi: apei: Do not panic() when correctable errors are marked as
fatal.
acpi: apei: Warn when GHES marks correctable errors as "fatal"
drivers/acpi/apei/ghes.c | 132 ++++++++++++++++++++++++++++++++++++++++-------
drivers/edac/ghes_edac.c | 3 +-
include/acpi/ghes.h | 5 +-
3 files changed, 117 insertions(+), 23 deletions(-)
--
2.14.3
Powered by blists - more mailing lists