linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH V3] acpi: apei: check for pending errors when probing GHES entries
@ 2017-05-18 21:22 Tyler Baicar
  2017-05-21 13:39 ` Borislav Petkov
  0 siblings, 1 reply; 2+ messages in thread
From: Tyler Baicar @ 2017-05-18 21:22 UTC (permalink / raw)
  To: rjw, lenb, bp, prarit, bhelgaas, punit.agrawal, mingo, linux-acpi,
	linux-kernel, shiju.jose, James.Morse, ahs3
  Cc: Tyler Baicar

Check for pending errors when probing GHES entries. It is possible
that a fatal error is already pending at this point, so we should
handle it as soon as the driver is probed. This also avoids a
potential issue if there was an interrupt that was already
cleared for an error since the GHES driver wasn't present.

V3: Check for pending errors of all GHES types

Signed-off-by: Tyler Baicar <tbaicar@codeaurora.org>
---
 drivers/acpi/apei/ghes.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
index d0855c0..5347230 100644
--- a/drivers/acpi/apei/ghes.c
+++ b/drivers/acpi/apei/ghes.c
@@ -1039,6 +1039,9 @@ static int ghes_probe(struct platform_device *ghes_dev)
 	}
 	platform_set_drvdata(ghes_dev, ghes);
 
+	/* Handle any pending errors right away */
+	ghes_proc(ghes);
+
 	return 0;
 err_edac_unreg:
 	ghes_edac_unregister(ghes);
-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.


^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-05-21 13:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-05-18 21:22 [PATCH V3] acpi: apei: check for pending errors when probing GHES entries Tyler Baicar
2017-05-21 13:39 ` Borislav Petkov

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).