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

Re: [Xen-devel] [PATCH] 14287 followup - console

  • To: Ben Thomas <bthomas@xxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Tue, 13 Mar 2007 09:33:40 +0000
  • Delivery-date: Tue, 13 Mar 2007 02:33:03 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdlUq7v7bH+4tFFEduMWwAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] 14287 followup - console

On 12/3/07 20:14, "Ben Thomas" <bthomas@xxxxxxxxxxxxxxx> 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

Xen-devel mailing list



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