WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH, RFC] linux Potential clean up of console transition
From: Bill Burns <bburns@xxxxxxxxxx>
Date: Mon, 08 Dec 2008 10:53:55 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 08 Dec 2008 07:54:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4939288A.2070508@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C55ED6F3.9C2%keir.fraser@xxxxxxxxxxxxx> <4939288A.2070508@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20080915)
Bill Burns wrote:
> Keir Fraser wrote:
>> On 05/12/2008 12:40, "Bill Burns" <bburns@xxxxxxxxxx> wrote:
>>
>>> 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.
>> It's done in vga_endboot too, if in a standard text mode. The code is
>> different in each case.
> 
> Ahh, sorry, rather than looking at the entire patch,
> I had just looked at 1 file....
> 
>  Thanks,
>  Bill


Tested out the change on x86_64 and it does not work for me.
The Xen messages remain on the console and with the
quiet kernel arg the user space output just intermixes
with it and it's unreadable. (Using quiet is key, as
non-quiet outputs so fast it's not possible to see
the issue).

 Bill



> 
>>  -- Keir
>>
>>
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel