diff options
| author | kfraser@localhost.localdomain <kfraser@localhost.localdomain> | 2006-08-10 10:39:58 +0100 |
|---|---|---|
| committer | kfraser@localhost.localdomain <kfraser@localhost.localdomain> | 2006-08-10 10:39:58 +0100 |
| commit | 3f31a200de12122fdc0a4031aed3a381ea7d4ed2 (patch) | |
| tree | a5e8388053d2a2acf4b9ff270b4df620d72e6203 | |
| parent | 2dcebc270eb1603d27436532cd40d8b682a25290 (diff) | |
| download | xen-3f31a200de12122fdc0a4031aed3a381ea7d4ed2.tar.gz xen-3f31a200de12122fdc0a4031aed3a381ea7d4ed2.tar.bz2 xen-3f31a200de12122fdc0a4031aed3a381ea7d4ed2.zip | |
[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@watson.ibm.com>
| -rw-r--r-- | linux-2.6-xen-sparse/drivers/xen/console/console.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/linux-2.6-xen-sparse/drivers/xen/console/console.c b/linux-2.6-xen-sparse/drivers/xen/console/console.c index ff1cfe2d7e..b9dd2f67b1 100644 --- a/linux-2.6-xen-sparse/drivers/xen/console/console.c +++ b/linux-2.6-xen-sparse/drivers/xen/console/console.c @@ -178,7 +178,7 @@ static struct tty_driver *kcons_device(struct console *c, int *index) 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; |