Re: [PATCH 0/7] Boot IRQ quirks and rerouting

[Maciej W. Rozycki]

On Wed, 4 Jun 2008, Jon Masters wrote:

> *). Top level handler is *tiny*. It's job is to get called (along with
> every other such function registered for a particular IRQ line) and
> determine if its device generated the interrupt, and to acknowledge,
> preventing the device from asserting the IRQ line any longer.
> 
> The top part is called in hard IRQ context, even on RT.
> 
> *). Bottom level is automatically scheduled by the kernel in response to
> the top part acknowledging that its device caused the interrupt.
> 
> The bottom part is run inside a dedicated kernel thread.

 I see what you mean -- well, with sane hardware that should be doable 
with little effort indeed.

  Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/