From: Bill Burns <bburns@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH, RFC] linux Potential clean up of console transition
Date: Mon, 08 Dec 2008 10:53:55 -0500 [thread overview]
Message-ID: <493D4313.1040202@redhat.com> (raw)
In-Reply-To: <4939288A.2070508@redhat.com>
Bill Burns wrote:
> Keir Fraser wrote:
>> On 05/12/2008 12:40, "Bill Burns" <bburns@redhat.com> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-12-08 15:53 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 ` [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 [this message]
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=493D4313.1040202@redhat.com \
--to=bburns@redhat.com \
--cc=keir.fraser@eu.citrix.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.