From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] 14287 followup - console
Date: Tue, 13 Mar 2007 09:33:40 +0000
Message-ID: <C21C2074.B562%keir@xensource.com>
References: <45F5B498.7010108@virtualiron.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45F5B498.7010108@virtualiron.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ben Thomas <bthomas@virtualiron.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 12/3/07 20:14, "Ben Thomas" <bthomas@virtualiron.com> wrote:

> Part of the original submission that resulted in 14287 was to catch
> all output to the console/vga. 14287, as committed, only captures
> a portion of the console output. The attached patch allows capture of
> the rest of the output.

The console ring is only for Xen output (and also, as it happens, HVM domU
bootstrap output since bytes output via port 0xe9 also get printk'ed). The
only other useful output would be from dom0, and you can already obtain that
via syslog. By not capturing dom0 output in the console ring we prevent
interactive sessions on the dom0 console from obliterating useful Xen debug
output which we may want to gather later (if we're not running an automatic
gatherer daemon). 

 -- Keir