Re: Multiple MSI, take 3


There is one idea that seems to model this cleanly
without breaking all kinds of expectations.

That is an irq with a very small data payload.

In that case we wire all of the vectors up to a single
irq handler that computes the payload as:
payload = vector - base-vector.

And then we figure out how to pass that to the handler in irqaction.

To most of the system it is a single irq so it avoids breaking
expectations about what an irq is.

To everything else it is a little odd, and has it's own unique
set of rules (which is good as well).

Eric
--
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/

Relevant Pages

  • Re: Multiple MSI, take 3
    ... without breaking all kinds of expectations. ... That is an irq with a very small data payload. ... To most of the system it is a single irq so it avoids breaking ...
    (Linux-Kernel)
  • Re: Multiple MSI, take 3
    ... That is an irq with a very small data payload. ... And then we figure out how to pass that to the handler in irqaction. ... * the interrupt handler to determine which vector was called. ...
    (Linux-Kernel)
  • Re: [PATCH 0/9] Remove irq argument from all irq handlers
    ... The practical question is how do we make this change without breaking ... the drivers that use their irq argument. ...
    (Linux-Kernel)