cvs commit: src/sys/alpha/alpha interrupt.c src/sys/alpha/isa isa.c src/sys/amd64/amd64 intr_machdep.c src/sys/amd64/include intr_machdep.h src/sys/amd64/isa atpic.c src/sys/arm/arm intr.c src/sys/dev/sio sio.c src/sys/dev/uart uart_kbd_sun.c uart_tty.c ...

[Gleb Smirnoff]

  John,

On Fri, Oct 28, 2005 at 10:41:42AM -0400, John Baldwin wrote:
J> > Of course the real challenge is to make things like the puc device do
J> > the right thing automatically instead of needing 'options
J> > PUC_FASTINTR'.
J> 
J> You mean like sio(4) tried to?  The problem is that with the previosu code if 
J> sio(4) went first, it would register INTR_FAST and some later PCI device 
J> wouldn't be able to register its interrupt.  There's not an easy solution to 
J> that problem if you want to keep the semantics that INTR_FAST implies 
J> INTR_EXCL.

is it possible to implement such a feature that driver requests INTR_FAST
and it succeds only and only if interrupt isn't shared?

For example I've got a console server with three puc devices. Since one of them
share its irq with ATA, I can't trun on PUC_FASTINTR on this box. However,
theoretically it is possible two make two pucs use a fast interrupt
handler and one not.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE