Subject: Re: Bug in x86 ioapic interrupt code for devices with shared interrupts?
To: Thor Lancelot Simon <firstname.lastname@example.org>
From: Manuel Bouyer <email@example.com>
Date: 03/03/2006 22:10:35
On Fri, Mar 03, 2006 at 04:02:19PM -0500, Thor Lancelot Simon wrote:
> On Fri, Mar 03, 2006 at 09:53:15PM +0100, Manuel Bouyer wrote:
> > BTW, I still don't understand why a driver couldn't claim an interrupt
> > even if it didn't generate it. AFAIK in the i386 interrupt code nothing
> > uses the return value. This is in i386/vector.S, in INTRSTUB.
> > >From what I understand in amd64/vector.S the return value is also ignored.
> > I'm probably missing something, but I fail to see what ...
> One problem is that it's not at all clear to me what putting the bge
> hardware in "in interrupt handler mitigation mode" if it did not
> actually interrupt you will do. That's what the next line of if_bge.c
Ha OK, so it's in the driver itself. I though we were talking about the
handler's return value ...
Manuel Bouyer <firstname.lastname@example.org>
NetBSD: 26 ans d'experience feront toujours la difference