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] how can native driver response quickly for low FIFO devi

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] how can native driver response quickly for low FIFO device
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Thu, 25 May 2006 21:53:20 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 25 May 2006 06:56:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ//N6AnrpuiwtESj+rWaqRiX6WXgABWeGg
Thread-topic: [Xen-devel] how can native driver response quickly for low FIFO device
> 
> There's a 128-byte receive buffer. Bytes are greedily taken from the
> UART FIFO in interrupt context and written to the software receive
> buffer. If overflow were a problem we could obviously quite easily
> make that receive buffer substantially larger.
But this need the participate of processor in dom0. If the physical
processor is running for domU, and domU is waiting for its time slice
(descheduled), how can the bytes be taken to software receive buffer?
Eddie

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