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] serial8250: too much work for irq4

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] serial8250: too much work for irq4
From: Markus Armbruster <armbru@xxxxxxxxxx>
Date: Wed, 18 Feb 2009 19:18:20 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 18 Feb 2009 10:18:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18844.18978.782069.848765@xxxxxxxxxxxxxxxxxxxxxxxx> (Ian Jackson's message of "Wed\, 18 Feb 2009 17\:49\:22 +0000")
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: <87ljs3ekxm.fsf@xxxxxxxxxxxxxxxxx> <C5C1F56E.2F2E%keir.fraser@xxxxxxxxxxxxx> <18844.18978.782069.848765@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> writes:

> Keir Fraser writes ("Re: [Xen-devel] serial8250: too much work for irq4"):
>> Perhaps we could add a qemu command-line option to force accurate uart
>> emulation w.r.t. programmed FIFO depth and baud rate? Then those who want
>> this more accurate but more expensive and slower behaviour can configure it.
>
> That would certainly be possible.  Our hw/serial.c is very like
> upstream's, and the same issue will apply to (for example) KVM, so we
> should coordinate any such change with upstream.  I would suggest we
> crosspost the patch to xen-devel and qemu-devel.
>
> Markus: are you sufficiently bothered about this that you'd like to
> supply a patch to change the behaviour in the way Keir suggests :-).
>
> Ian.

;)

I don't yet know.  I need to try the other patch you mentioned, and see
how the that flies.  Anyway, the proposed change should most probably be
routed through upstream QEMU.

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