Messages in this thread | | | Date | Fri, 3 Sep 1999 12:44:22 -0700 | From | Brian Swetland <> | Subject | Re: Shared interrupt (lack of) handling |
| |
[Gerard Roudier <groudier@club-internet.fr>] > > > One thing that you could do with the I_DID_SOME_STUFF flag is use the > > statistics to reorder the execution of interrupt handlers so that the > > device that causes the most interrupts gets called first. Might be > > cool, difficult to tell. > > You _must_ call all interrupt handlers that requested the same IRQ when > this IRQ is raised. So your flag does not optimize anything.
One thing it does help with is to identify a situation where an interrupt is occurring but no installed drivers are responding to it. Buggy hardware or a buggy driver causing interrupts other than ones it's handling to occur can result in this sort of thing. If a PCI interrupt is triggering continuously and nobody is handling it (though somebody has an interrupt handler installed) it is sometimes nice to let the system know.
That interrupt could be temporarily masked, warnings could be injected into logs, etc.
Brian
-- Brian Swetland | Kernel Engineer | "Home is where the dot files are." swetland@be.com | Be Incorporated | -- Keith Garner
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |