[XenPPC] [linux-ppc-2.6] [POWERPC] all xen consoles must have CON_ENABLED set

[Xen patchbot-linux-ppc-2.6 <patchbot-linux-ppc-2.6@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
# Node ID 914274c1c3c97e6f2cc982ec9de491c6b80604ae
# Parent  417779fda95b8b8f204cde0be75c56cccac55536
[POWERPC] all xen consoles must have CON_ENABLED set

patch submitted upstream.

I cannot think of any circumstance that the Xen console device would
not have CON_ENABLED.  With out this, DomUs that panic() before the
init process has started (and maybe even after) do not get output hi
priority log_levels (like panic()) from LOG_BUF().

Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
---
 drivers/xen/console/console.c |    4 +---
 1 files changed, 1 insertion(+), 3 deletions(-)

diff -r 417779fda95b -r 914274c1c3c9 drivers/xen/console/console.c
--- a/drivers/xen/console/console.c     Wed Aug 09 18:33:27 2006 -0400
+++ b/drivers/xen/console/console.c     Wed Aug 09 21:32:15 2006 -0400
@@ -178,7 +178,7 @@ static struct tty_driver *kcons_device(s
 
 static struct console kcons_info = {
        .device = kcons_device,
-       .flags  = CON_PRINTBUFFER,
+       .flags  = CON_PRINTBUFFER | CON_ENABLED,
        .index  = -1,
 };
 
@@ -192,8 +192,6 @@ static int __init xen_console_init(void)
                if (xc_mode == XC_DEFAULT)
                        xc_mode = XC_SERIAL;
                kcons_info.write = kcons_write_dom0;
-               if (xc_mode == XC_SERIAL)
-                       kcons_info.flags |= CON_ENABLED;
        } else {
                if (xc_mode == XC_DEFAULT)
                        xc_mode = XC_TTY;

_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel