Date: Thu, 17 Jun 2004 21:19:36 +0400 From: Roman Kurakin <rik@cronyx.ru> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-current@freebsd.org Subject: Re: How to catch interrupt Message-ID: <40D1D2A8.2070000@cronyx.ru> In-Reply-To: <20040617164703.H2144@gamplex.bde.org> References: <40D070B7.5000009@cronyx.ru> <20040617080547.F8883@gamplex.bde.org> <40D0CABA.1020101@cronyx.ru> <20040617164703.H2144@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: >On Thu, 17 Jun 2004, Roman Kurakin wrote: > > >>Bruce Evans: >> >> >>>However, you may only need to test for pending interrupts. This can >>>be done for isa interrupts using isa_irq_pending() to get a bitmap of >>> >>> >>It seems that this function is not working for interrupts that were >>already used >>by some driver before I call it. >> >> > >It only works for unacknowledged interrupts, so it can only work for >masked interrupts. See sio.c: > > >% /* >% * We don't want to get actual interrupts, just masked ones. >% * Interrupts from this line should already be masked in the ICU, >% * but mask them in the processor as well in case there are some >% * (misconfigured) shared interrupts. >% */ >% mtx_lock_spin(&sio_lock); > >Note that masking interrupts in the processor only helps for the non-SMP >case, and the comment has rotted: >- the code acquires a spinlock. It only masks interrupts as a BAD side > effect. In my version, acquiring a spinlock doesn't mask processor > interrupts, and there is an explicit intr_disable(). >- interrupts can now be shared in some non-misconfigured cases. > > So spin lock should help me in some cases but there is other cases were this wouldn't help or I miss smth? In this case if some driver will acquire interrupt while probing and after this it will release it (for example it will decide that this is wrong intr and will try other), and after we will try to load sio driver we may fail to load it case we would unable to check this intr line. rik >Bruce >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40D1D2A8.2070000>