All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Bill Burns <bburns@redhat.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH, RFC] linux Potential clean up of console transition
Date: Fri, 05 Dec 2008 11:50:34 +0000	[thread overview]
Message-ID: <C55EC60A.9AF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4938580D.7060806@redhat.com>

On 04/12/2008 22:22, "Bill Burns" <bburns@redhat.com> wrote:

> 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.

I think it's better for Xen to clear the screen when it relinquishes the
console. I've checked in a patch to do that. It still leaves the screen
uncleared if the 'keep vga' option is specified to Xen (that's the mode
where Xen tries to share with dom0, for debugging purposes). In that mode it
seems unwise to clear screen data when we don't have to.

Jan talked about orig_x and orig_y but we don't actually pass such data to
dom0 for vesa consoles, so there's no trivial solution there. I think what
we have now is fine, since debuggability is still available by specifying
that Xen share the vga console with dom0.

 -- Keir

  parent reply	other threads:[~2008-12-05 11:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 22:22 [PATCH, RFC] linux Potential clean up of console transition Bill Burns
2008-12-05 11:00 ` [PATCH,RFC] " Jan Beulich
2008-12-05 12:31   ` Bill Burns
2008-12-05 11:50 ` Keir Fraser [this message]
2008-12-05 12:35   ` [PATCH, RFC] " 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=C55EC60A.9AF%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=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.