From: Bill Burns <bburns@redhat.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH, RFC] linux Potential clean up of console transition
Date: Thu, 04 Dec 2008 17:22:05 -0500 [thread overview]
Message-ID: <4938580D.7060806@redhat.com> (raw)
When using a video monitor for the console there is
an issue with the transition between Hypervisor
output and dom0 output (this is at least true in
3.1.2/2.6.18 vintage systems).
What happens is that the screen is full of the (XEN)
messages and then the dom0 kernel starts off at the top
of the screen and over prints until the screen starts
to scroll. It's not all that noticeable since the
output tends to be blow right past the issue.
But when the "quiet" boot arg is used for the dom0
kernel it can be user space output that collides and
that can pose a problem. Like when a prompt for
an encrypted file system cannot be read due to the
mess on the screen.
Below is a crude little loop that could be used to
avoid the issue by outputting newlines to push
the beginning of dom0's output to the bottom of
the screen. Other suggestions are welcome. Note
is uses KERN_ERR since "quiet" blocks output
at the default printk level.
Bill
--- drivers/xen/console/console.c.orig 2008-10-21 15:26:25.000000000 -0400
+++ drivers/xen/console/console.c 2008-12-04 17:23:12.000000000 -0500
@@ -192,6 +192,8 @@ static struct console kcons_info = {
static int __init xen_console_init(void)
{
+ int i;
+
if (!is_running_on_xen())
goto out;
@@ -230,6 +232,10 @@ static int __init xen_console_init(void)
register_console(&kcons_info);
+ if (screen_info.orig_video_mode == 3) {
+ for (i = 0; i < screen_info.orig_video_lines; i++)
+ printk(KERN_ERR "\n");
+ }
out:
return 0;
}
next reply other threads:[~2008-12-04 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 22:22 Bill Burns [this message]
2008-12-05 11:00 ` [PATCH,RFC] linux Potential clean up of console transition Jan Beulich
2008-12-05 12:31 ` Bill Burns
2008-12-05 11:50 ` [PATCH, RFC] " Keir Fraser
2008-12-05 12:35 ` Bill Burns
2008-12-05 12:40 ` Bill Burns
2008-12-05 13:02 ` Keir Fraser
2008-12-05 13:11 ` Bill Burns
2008-12-08 15:53 ` Bill Burns
2008-12-09 13:24 ` Keir Fraser
2008-12-11 13:00 ` Bill Burns
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4938580D.7060806@redhat.com \
--to=bburns@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.