From 6016c522c6d6e7d6cce385379cfbe8f06cf8048e Mon Sep 17 00:00:00 2001 From: Levi Yun Date: Thu, 19 Sep 2024 16:24:43 +0100 Subject: [PATCH] StandaloneMmCore: Change log level when mCommunicationBuffer is NULL On Arm all requests are handled as Asynchronous events by the Root MMI handler. Since the communication data is conveyed using either the NS shared buffer or the Secure shared buffer, the Arm implementation does not setup the mCommunicationBuffer. Therefore, the mCommunicationBuffer being NULL is not an error case. Moreover, the existing code switches to Asynchronous event processing when the mCommunicationBuffer is NULL, which means that the log is an info log rather than an error. Therefore, change the log level from ERROR to INFO when the mCommunicationBuffer is NULL. Signed-off-by: Levi Yun --- StandaloneMmPkg/Core/StandaloneMmCore.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/StandaloneMmPkg/Core/StandaloneMmCore.c b/StandaloneMmPkg/Core/StandaloneMmCore.c index 12d36fe35d..3870bafc9d 100644 --- a/StandaloneMmPkg/Core/StandaloneMmCore.c +++ b/StandaloneMmPkg/Core/StandaloneMmCore.c @@ -581,7 +581,7 @@ MmEntryPoint ( } } } else { - DEBUG ((DEBUG_ERROR, "No valid communication buffer, no Synchronous MMI will be processed\n")); + DEBUG ((DEBUG_INFO, "No valid communication buffer, no Synchronous MMI will be processed\n")); } //