[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH, RFC] linux Potential clean up of console transition

  • To: Bill Burns <bburns@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Fri, 05 Dec 2008 11:50:34 +0000
  • Cc:
  • Delivery-date: Fri, 05 Dec 2008 03:51:30 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclWz65Y889psaFUokiPHRmpobMrpA==
  • Thread-topic: [Xen-devel] [PATCH, RFC] linux Potential clean up of console transition

On 04/12/2008 22:22, "Bill Burns" <bburns@xxxxxxxxxx> 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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.