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] [PATCH] add polling support for ns16550

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] add polling support for ns16550
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Thu, 24 Nov 2005 07:07:10 -0700
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 24 Nov 2005 14:07:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f9c1abc6d99234e02c71b287907174ea@xxxxxxxxxxxx>
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>
Organization: OSLO R&D
References: <1132764049.18843.7.camel@tdi> <f9c1abc6d99234e02c71b287907174ea@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2005-11-24 at 11:13 +0000, Keir Fraser wrote:
> On 23 Nov 2005, at 16:40, Alex Williamson wrote:
> 
> >   The patch below adds ac_timer based polling to the ns16550 UART
> > driver.  This is useful when the interrupt line is not connected in
> > hardware or the mechanism to enable it is not readily available in the
> > hypervisor.  Polling is only enabled when the UART IRQ is set to zero.
> > Thanks,
> 
> I reworked the patch a little and checked it in, thanks.

   Thanks!

> One thing I removed was the clear-and-reset of IER in the timeout 
> handler. Given we write zero to IER in the preirq steup function, and 
> also we do not set the master-enable bit in the MCR, I cannot see how 
> you could end up accidentally fielding interrupts in the timeout 
> handler. Did I miss something?

   It was mainly paranoia, but on ia64 we don't have a good way to hide
UARTs from the guest domains, so it's possible that a dom0 with 8250
support will enable those bits on the UART.  All sorts of strange things
happen when the hypervisor and a guest compete for access to a UART, but
I thought I would at least avoid the hypervisor polling triggering the
real interrupt.  I'm ok with dropping it, the UART isn't really
functional no matter what paranoia checks are added when multiple
drivers are competing to use it.  Thanks,

        Alex


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

<Prev in Thread] Current Thread [Next in Thread>