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

[Xen-devel] serial8250: too much work for irq4

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] serial8250: too much work for irq4
From: Markus Armbruster <armbru@xxxxxxxxxx>
Date: Tue, 17 Feb 2009 14:35:15 +0100
Delivery-date: Tue, 17 Feb 2009 05:35:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
I've seen $subject on RHEL-5 hvm guests in a RHEL-5 host with vpcus=2
when I hammer the serial console, e.g. with "od -a /boot/vmlinuz".  I
wonder whether the problem exists in xen-unstable as well.

Wild guess: Unlike a real UART, the virtual UART empties as quickly as
the kernel can stuff in bytes.  So, while the kernel has bytes to stuff,
it doesn't get around to doing much else.

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