[PATCH V2] powernv/hmi: Use the "unknown" checkstop type as a fallback

Subsystems: linux for powerpc (32-bit and 64-bit), the rest

STALE3767d REVIEWED: 2 (0M)

2 review trailers.

2 messages, 2 authors, 2016-04-11 · open the first message on its own page

[PATCH V2] powernv/hmi: Use the "unknown" checkstop type as a fallback

From: Russell Currey <hidden>
Date: 2016-03-15 10:14:28

The HMI code knows about three types of errors: CORE, NX and UNKNOWN.
If OPAL were to add a new type, it would not be handled at all since
there is no fallback case.  Instead of explicitly checking for UNKNOWN,
treat any checkstop type without a handler as unknown.

Signed-off-by: Russell Currey <redacted>
Reviewed-by: Daniel Axtens <redacted>
Reviewed-by: Andrew Donnellan <redacted>
---
V2: Print the type in the error message thanks to Andrew and Michael
---
 arch/powerpc/platforms/powernv/opal-hmi.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-hmi.c b/arch/powerpc/platforms/powernv/opal-hmi.c
index d000f4e..38dd321 100644
--- a/arch/powerpc/platforms/powernv/opal-hmi.c
+++ b/arch/powerpc/platforms/powernv/opal-hmi.c
@@ -150,15 +150,17 @@ static void print_nx_checkstop_reason(const char *level,
 static void print_checkstop_reason(const char *level,
 					struct OpalHMIEvent *hmi_evt)
 {
-	switch (hmi_evt->u.xstop_error.xstop_type) {
+	uint8_t type = hmi_evt->u.xstop_error.xstop_type;
+	switch (type) {
 	case CHECKSTOP_TYPE_CORE:
 		print_core_checkstop_reason(level, hmi_evt);
 		break;
 	case CHECKSTOP_TYPE_NX:
 		print_nx_checkstop_reason(level, hmi_evt);
 		break;
-	case CHECKSTOP_TYPE_UNKNOWN:
-		printk("%s	Unknown Malfunction Alert.\n", level);
+	default:
+		printk("%s	Unknown Malfunction Alert of type %d\n",
+		       level, type);
 		break;
 	}
 }
-- 
2.7.3

Re: [V2] powernv/hmi: Use the "unknown" checkstop type as a fallback

From: Michael Ellerman <mpe@ellerman.id.au>
Date: 2016-04-11 12:35:15

On Tue, 2016-15-03 at 10:14:12 UTC, Russell Currey wrote:
The HMI code knows about three types of errors: CORE, NX and UNKNOWN.
If OPAL were to add a new type, it would not be handled at all since
there is no fallback case.  Instead of explicitly checking for UNKNOWN,
treat any checkstop type without a handler as unknown.

Signed-off-by: Russell Currey <redacted>
Reviewed-by: Daniel Axtens <redacted>
Reviewed-by: Andrew Donnellan <redacted>
Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/f8a25db47ebc11fe228735d916

cheers
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help