From: Anthony Liguori <aligu...@amazon.com> Only print the banner if the log threshold is at least info.
For Vixen guests, we want the console output to be exactly what the PV guest would show on it's own. That means the inner Xen banner can potentially break automation that assumes a specific type of console output. Signed-off-by: Anthony Liguori <aligu...@amazon.com> --- xen/drivers/char/console.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/xen/drivers/char/console.c b/xen/drivers/char/console.c index 0f85707..3eb130d 100644 --- a/xen/drivers/char/console.c +++ b/xen/drivers/char/console.c @@ -812,9 +812,12 @@ void __init console_init_preirq(void) serial_set_rx_handler(sercon_handle, serial_rx); /* HELLO WORLD --- start-of-day banner text. */ - spin_lock(&console_lock); - __putstr(xen_banner()); - spin_unlock(&console_lock); + if ( 2 < xenlog_lower_thresh ) { + /* Only display at XENLOG_INFO level */ + spin_lock(&console_lock); + __putstr(xen_banner()); + spin_unlock(&console_lock); + } printk("Xen version %d.%d%s (%s@%s) (%s) debug=%c " gcov_string " %s\n", xen_major_version(), xen_minor_version(), xen_extra_version(), xen_compile_by(), xen_compile_domain(), -- 1.9.1 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel