From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen Mailing List <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] add polling support for ns16550
Date: Thu, 24 Nov 2005 07:07:10 -0700 [thread overview]
Message-ID: <1132841230.3074.20.camel@localhost.localdomain> (raw)
In-Reply-To: <f9c1abc6d99234e02c71b287907174ea@cl.cam.ac.uk>
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
prev parent reply other threads:[~2005-11-24 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 16:40 [PATCH] add polling support for ns16550 Alex Williamson
2005-11-24 11:13 ` Keir Fraser
2005-11-24 14:07 ` Alex Williamson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1132841230.3074.20.camel@localhost.localdomain \
--to=alex.williamson@hp.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.