Skip to content

ARM perf updates for 3.7

Hui Wang linux-arm-kernel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 9 patches 3 repliesIn review

Patches in v1 No applies recorded yet

None of the 9 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.

Read the v1 thread

Cover letter [PATCH 0/9] ARM perf updates for 3.7
Quoted 25 lines · Will Deacon
Quoted 2 lines · Hui Wang

Hi Will Deacon,

Hello,

Quoted 9 lines

For SMP platforms, each CPU core has an independent PMU, and each PMU has a dedicated irq (SPI or PPI). Current perf subsystem framework only supports each PMU to have a dedicated SPI irq, and it will support each PMU to have a PPI irq (i have seen someone has sent out the patches), but there is a situation the subsystem doesn't support yet, the situation is multi PMUs share one same SPI irq, e.g. the i.MX6Quad CPU has 4 cortex-a9 cores, each core has a PMU, all PMU irqs are routed (ORed) to one SPI irq, do you know how to support this situation?

That's what I like to call a braindead, broken system. Seriously, CPU PMU interrupts *can only* be handled on the CPU which raised them -- ORing these things together means ping-ponging the interrupt affinity around until we find the right guy. There's also the fun case where multiple PMUs assert simultaneously and I've even heard about platforms where they OR in the bloody L2 PMU interrupt as well for good measure!

Quoted 8 lines

If you have to support such a device, take a look at the ux500 code (db8500_pmu_handler), but please take all of your profiling numbers with a pinch of salt. For a quad-core processor, the numbers will probably be even less accurate.

Also, please go ahead and inflict sufficient injuries to your hardware guys that they stop this madness!

Got it, thanks for the information, it is very useful.

Regards,
Hui.

Quoted 3 lines

Will