[Xen-changelog] [xen-unstable] [CONSOLE] Always specify CON_ENABLED in Linux ocnsole driver.

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kfraser@xxxxxxxxxxxxxxxxxxxxx
# Node ID 485baffca4fdfd0568f51d230830f23b48db1a09
# Parent  cfd9d4601022e182c77c37ae1a7c08c1b082fa97
[CONSOLE] Always specify CON_ENABLED in Linux ocnsole driver.

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>
---
 linux-2.6-xen-sparse/drivers/xen/console/console.c |    4 +---
 1 files changed, 1 insertion(+), 3 deletions(-)

diff -r cfd9d4601022 -r 485baffca4fd 
linux-2.6-xen-sparse/drivers/xen/console/console.c
--- a/linux-2.6-xen-sparse/drivers/xen/console/console.c        Thu Aug 10 
10:37:15 2006 +0100
+++ b/linux-2.6-xen-sparse/drivers/xen/console/console.c        Thu Aug 10 
10:39:58 2006 +0100
@@ -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-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog