ARM: Dynamic IRQ demux support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 8 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 8 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/08] ARM: Dynamic IRQ demux support
Quoted 86 lines · Magnus Damm
Quoted 27 lines · Eric Miao
Quoted 21 lines · Magnus Damm
Quoted 8 lines · Eric Miao
Quoted 1 line · Magnus Damm
ARM: Dynamic IRQ demux support
Just FYI, I had a patch months ago for this:
http://www.spinics.net/linux/lists/arm-kernel/msg92836.html
Do you think that's a simpler way to go?
Thanks for the pointer. I wasn't aware of your patch, but the fact that both of us came up with similar solutions to the same problem clearly shows that there is a need for this feature.
Your patch is much less intrusive compared to what i came up with. I like the simplicity. I guess it is natural that the simplicity comes with a bit of overhead. I'm thinking of the extra branches and whatever potential cache misses coming from the code and callback being located in different cache lines compared to the rest of the code in
__irq_svcand__irq_usr.Quoted 4 lines
My patches keeps the handlers in the same cache lines as before, but this comes with the cost of more serious rearrangement of the code. Also, my
alignment_trappatch may decrease performance, not sure how to deal with that in a good way.Quoted 7 lines
Yeah, I was thinking of the performance degradation at that time as well. What worried me most is actually the long jump. However, we do have a long jump to
asm_do_IRQanyway.And the optimizations like
get_irqnr_preambleandget_irqnr_and_basecan be carried out in C code as well, or if that's tricky enough, inline assembly code can also help.Sure, I agree.
Quoted 11 lines
Quoted 7 lines
I don't mind so much which patch that gets merged, but I'm a little bit concerned about code duplication. My patch moves macros into a header file that each demux instance can make use of to minimize the amount of duplicated code. I'm not sure how you are planning on implementing each demux instance. If possible I'd like to see the
irq_handlermacro in a header file somewhere so we don't have to duplicate that code.Machines will have to specify their IRQ demux handler, which could be same among a group of machines which share common demux code, and thus duplication can be avoided.
Right, I agree. I'm thinking of SMP-specific interrupts for IPIs and local timers that most likely want to be shared across multiple machines. I can for instance imagine a wide range of Cortex-A9 based SoCs that all need to deal with SMP interrupts.
Quoted 5 lines
Quoted 2 lines
On top of that I'd also like to break out the GIC demux code and put it in a central location, but that's a separate issue.
I think we can make a common function call for all the IRQ demux handler for GIC then.
Sure, as long as we can point out the SoC-specific base address then we should be ok.
Quoted 11 lines
Quoted 2 lines
Any thoughts? Shall I try to move the
irq_handlermacro to some header file?Your patch is excellent, I don't mind either which gets in. What I'm a bit concerned is the effort to keep up with the mostly optimized code. I was thinking of a bit (not that much significant I guess) performance loss when multiple IRQ demux handler is required for the sake of simplicity and less intrusiveness, while still able to use the original optimized path when that's not required (i.e. turning
CONFIG_.... off).Thoughts?
I feel that the current abstraction with the macros in
entry-macros.Sis pretty nice and familiar. I think your solution with abstracting at theirq_handlerlevel is simple from the mach-programmers point of view, but it does come with some performance penalty. I'm also not so sure how to deal with the code duplication. Like you say, the code could be shared between machines, but exactly how I don't know.Did you hear anything back from Russell? If he's ok with your patch then problem solved. Perhaps it's already in the tracker? =)
Quoted 8 lines
If not, how about picking out the best part of our patches? I think my main benefit is the performance - hooking in the per-mach handlers below the
vector_stubcomes with little or no additional cost. Your strength is the simplicity and the nice use of themachine_desc. Perhaps we can put the__irq_usrand__irq_svccallbacks in structmachine_desc?Does anyone else care? =)
I care, but I haven't been able to dig into the details. The way things are going, I probably won't be able to either until after Linux Plumbers is over.
g.