On 11/30/2015 11:59 AM, Qais Yousef wrote:
On 11/30/2015 11:22 AM, Thomas Gleixner wrote:
Well, the question is why can't those functions not all use the raw
hardware irq. We have it in irq_data exactly to avoid calculations in
the hot path functions.
I'll see what I can do as part of this series. I think I can fix the
new IPI and device domains, but can't promise about the root gic
domain. It might be too big of a change for this series.
Unfortunately this is more work than I can afford putting into it right
now. Can we have this fix coming in later? It shouldn't affect anything
in this series.
The major issue here is that I need to split the root domain into shared
and local so that each will have its linear hwirq space therefore get
rid of the conversion macros.
BUT, the DT binding will break if I do this. I can't think of a simple
way to keep the existing binding and do the split. Not without hackery
and more magic at least which I don't think would be a better alternative.
Thanks,
Qais
