From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Burns Subject: Re: [PATCH, RFC] linux Potential clean up of console transition Date: Fri, 05 Dec 2008 07:40:50 -0500 Message-ID: <49392152.1030508@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 04/12/2008 22:22, "Bill Burns" 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. > Hmm, looked at the patch and you did the work in vesa_endboot, which really only exists in x86_64. So this only solves the issue for that platform. I had been fiddling in vga_endboot to work around that when I was looking at a HV fix. Bill > -- Keir > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel