On Fri, Feb 13, 2015 at 08:56:12AM -0500, Thor Lancelot Simon wrote: > But it looks like Tom's still getting the interrupt, which means, at least, > that he's paying the overhead of a quick "Nope, no handler for this one!" > return from the interrupt handling code. How far upstream is it possible > to disable or mask it, I wonder, without breaking another device you care > about or having to switch *it* to polled mode?
That's the part that doesn't make sense to me. For a PCI device, the interrupt is level triggered, so unless the problem is the *querying* in the interrupt handler, the interrupt itself can't be the problem. Joerg
