Date: Fri, 28 Oct 2005 20:02:18 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Mark Linimon <linimon@lonesome.com>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Peter Wemm <peter@wemm.org>, cvs-src@FreeBSD.org Subject: Re: 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 ... Message-ID: <20051028160218.GJ41520@cell.sick.ru> In-Reply-To: <200510281041.44147.jhb@freebsd.org> References: <200510251948.j9PJmmmj043891@repoman.freebsd.org> <200510261320.46985.jhb@freebsd.org> <200510261648.27126.peter@wemm.org> <200510281041.44147.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051028160218.GJ41520>