[Skiboot] [PATCH 3/3] secvar_main: increase verbosity of the main entrypoint

[Eric Richter]

This patch simply adds unconditional log entries at the beginning and
end of secvar initialization, to clarify whether secvar support is
enabled and functional.

Signed-off-by: Eric Richter <erichte at linux.ibm.com>
---
 libstb/secvar/secvar_main.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/libstb/secvar/secvar_main.c b/libstb/secvar/secvar_main.c
index fc5527ab..692ac8c2 100644
--- a/libstb/secvar/secvar_main.c
+++ b/libstb/secvar/secvar_main.c
@@ -27,6 +27,8 @@ int secvar_main(struct secvar_storage_driver storage_driver,
 {
 	int rc = OPAL_UNSUPPORTED;
 
+	prlog(PR_INFO, "Secure variables are supported, initializing secvar\n");
+
 	secvar_storage = storage_driver;
 	secvar_backend = backend_driver;
 
@@ -78,10 +80,12 @@ int secvar_main(struct secvar_storage_driver storage_driver,
 	if (rc)
 		goto out;
 
+	prlog(PR_INFO, "secvar initialized successfully\n");
+
 	return OPAL_SUCCESS;
 fail:
 	secvar_set_status("fail");
 out:
-	printf("Secure Variables Status %04x\n", rc);
+	printf("secvar failed to initialize, rc = %04x\n", rc);
 	return rc;
 }
-- 
2.21.0