xsm: remove printing from set_to_dummy_if_null()

Filling dummy module's hook to null value of xsm_operations structure
will generate debug message. This becomes boot time spew for module
like silo, which only sets a few hooks of itself. So remove the printing
to avoid boot time spew.

Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
Signed-off-by: Xin Li <xin.li@citrix.com>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>

diff --git a/xen/xsm/dummy.c b/xen/xsm/dummy.c
index 06a674fad06e9c9ed1972022a3cdcc95e2866fbf..5701047c06fb2f797745ad2f006236d4a55432ef 100644 (file)
--- a/xen/xsm/dummy.c
+++ b/xen/xsm/dummy.c
@@ -18,12 +18,7 @@ struct xsm_operations dummy_xsm_ops;
 #define set_to_dummy_if_null(ops, function)                            \
     do {                                                               \
         if ( !ops->function )                                          \
-        {                                                              \
             ops->function = xsm_##function;                            \
-            if (ops != &dummy_xsm_ops)                                 \
-                dprintk(XENLOG_DEBUG, "Had to override the " #function \
-                    " security operation with the dummy one.\n");      \
-        }                                                              \
     } while (0)
 
 void __init xsm_fixup_ops (struct xsm_operations *ops)