| Message ID | 1425475545-4323-1-git-send-email-daniel.thompson@linaro.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi Daniel, On Wed, Mar 04, 2015 at 01:25:45PM +0000, Daniel Thompson wrote: > Some ARM platforms mux the PMU interrupt of every core into a single > SPI. On such platforms if the PMU of any core except 0 raises an interrupt > then it cannot be serviced and eventually, if you are lucky, the spurious > irq detection might forcefully disable the interrupt. > > On these SoCs it is not possible to determine which core raised the > interrupt so workaround this issue by queuing irqwork on the other > cores whenever the primary interrupt handler is unable to service the > interrupt. > > The u8500 platform has an alternative workaround that dynamically alters > the affinity of the PMU interrupt. This workaround logic is no longer > required so the original code is removed as is the hook it relied upon. > > Tested on imx6q (which has fours cores/PMUs all muxed to a single SPI) > using a simple soak, combined perf and CPU hotplug soak and using > perf fuzzer's fast_repro.sh. [...] > diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h > index b1596bd59129..dfef7904b790 100644 > --- a/arch/arm/include/asm/pmu.h > +++ b/arch/arm/include/asm/pmu.h > @@ -87,6 +87,14 @@ struct pmu_hw_events { > * already have to allocate this struct per cpu. > */ > struct arm_pmu *percpu_pmu; > + > +#ifdef CONFIG_SMP > + /* > + * This is used to schedule workaround logic on platforms where all > + * the PMUs are attached to a single SPI. > + */ > + struct irq_work work; > +#endif > }; > > struct arm_pmu { > @@ -117,6 +125,10 @@ struct arm_pmu { > struct platform_device *plat_device; > struct pmu_hw_events __percpu *hw_events; > struct notifier_block hotplug_nb; > +#ifdef CONFIG_SMP > + int muxed_spi_workaround_irq; > + atomic_t remaining_irq_work; > +#endif > }; > > #define to_arm_pmu(p) (container_of(p, struct arm_pmu, pmu)) > diff --git a/arch/arm/kernel/perf_event.c b/arch/arm/kernel/perf_event.c > index 557e128e4df0..e3fc1a0ce969 100644 > --- a/arch/arm/kernel/perf_event.c > +++ b/arch/arm/kernel/perf_event.c > @@ -305,8 +305,6 @@ validate_group(struct perf_event *event) > static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) > { > struct arm_pmu *armpmu; > - struct platform_device *plat_device; > - struct arm_pmu_platdata *plat; > int ret; > u64 start_clock, finish_clock; > > @@ -317,14 +315,9 @@ static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) > * dereference. > */ > armpmu = *(void **)dev; > - plat_device = armpmu->plat_device; > - plat = dev_get_platdata(&plat_device->dev); > > start_clock = sched_clock(); > - if (plat && plat->handle_irq) > - ret = plat->handle_irq(irq, armpmu, armpmu->handle_irq); > - else > - ret = armpmu->handle_irq(irq, armpmu); > + ret = armpmu->handle_irq(irq, armpmu); > finish_clock = sched_clock(); > > perf_sample_event_took(finish_clock - start_clock); > diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c > index 61b53c46edfa..d5bbd79abd4c 100644 > --- a/arch/arm/kernel/perf_event_cpu.c > +++ b/arch/arm/kernel/perf_event_cpu.c > @@ -59,6 +59,116 @@ int perf_num_counters(void) > } > EXPORT_SYMBOL_GPL(perf_num_counters); > > +#ifdef CONFIG_SMP > + > +static cpumask_t down_prepare_cpu_mask; > +static DEFINE_SPINLOCK(down_prepare_cpu_lock); > + > +/* > + * Workaround logic that is distributed to all cores if the PMU has only > + * a single IRQ and the CPU receiving that IRQ cannot handle it. Its > + * job is to try to service the interrupt on the current CPU. It will > + * also enable the IRQ again if all the other CPUs have already tried to > + * service it. > + */ > +static void cpu_pmu_do_percpu_work(struct irq_work *w) > +{ > + struct pmu_hw_events *hw_events = > + container_of(w, struct pmu_hw_events, work); > + struct arm_pmu *cpu_pmu = hw_events->percpu_pmu; > + > + /* Ignore the return code, we can do nothing useful with it */ > + (void) cpu_pmu->handle_irq(0, cpu_pmu); > + > + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) > + enable_irq(cpu_pmu->muxed_spi_workaround_irq); > +} > + > +/* > + * Workaround for systems where all PMU interrupts are targeting a > + * single SPI. > + * > + * The workaround will disable the interrupt and distribute irqwork to all > + * the other processors in the system. Hopefully one of them will clear the > + * interrupt... > + * > + * The workaround is only deployed when all PMU interrupts are aimed > + * at a single core. As a result the workaround is never re-entered > + * making it safe for us to use static data to maintain state. > + */ > +static void cpu_pmu_deploy_muxed_spi_workaround(struct arm_pmu *cpu_pmu) > +{ > + static cpumask_t irqwork_mask; > + int cpu; > + > + disable_irq_nosync(cpu_pmu->muxed_spi_workaround_irq); > + spin_lock(&down_prepare_cpu_lock); > + > + /* > + * Combining cpu_online_mask and down_prepare_cpu_mask gives > + * us the CPUs that are currently online and cannot die until > + * we release down_prepare_cpu_lock. > + */ > + cpumask_andnot(&irqwork_mask, cpu_online_mask, &down_prepare_cpu_mask); > + cpumask_clear_cpu(smp_processor_id(), &irqwork_mask); > + atomic_add(cpumask_weight(&irqwork_mask), &cpu_pmu->remaining_irq_work); AFAICT, this is a hack to avoid get_online_cpus (which can sleep) from irq context? Is there no way we can do try_get_online_cpus, and just return IRQ_NONE if that fails? At some point, the hotplug operation will complete and we'll be able to service the pending interrupt. I think that would allow us to kill the down_prepare_cpu_lock. Will
Hi Daniel, I'd very much like to see us converge on a solution for this soon. The existing hack is getting in the way of other rework of the arm/arm64 perf code. I think the approach this patch takes should work, but there are some parts that can be cleaned up (hopefully mostly cosmetic). Unfortunately I don't seem to have a relevant platform for testing on. [...] > diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h > index b1596bd59129..dfef7904b790 100644 > --- a/arch/arm/include/asm/pmu.h > +++ b/arch/arm/include/asm/pmu.h > @@ -87,6 +87,14 @@ struct pmu_hw_events { > * already have to allocate this struct per cpu. > */ > struct arm_pmu *percpu_pmu; > + > +#ifdef CONFIG_SMP > + /* > + * This is used to schedule workaround logic on platforms where all > + * the PMUs are attached to a single SPI. > + */ > + struct irq_work work; > +#endif > }; > > struct arm_pmu { > @@ -117,6 +125,10 @@ struct arm_pmu { > struct platform_device *plat_device; > struct pmu_hw_events __percpu *hw_events; > struct notifier_block hotplug_nb; > +#ifdef CONFIG_SMP > + int muxed_spi_workaround_irq; There's nothing workaround specific about this IRQ; it's just the only IRQ. I think we should just pre-parse all the IRQs into a list at probe time, regardless of SMP or the workaround. Then we can just grab the first (and only) interrupt from the list in the workaround paths, and otherwise just iterate over the list. > + atomic_t remaining_irq_work; Perhaps remaining_work_irqs? That would make it clear that this is a counter rather than a boolean or enumeration. We could s/work/fake/ or something to that effect. > @@ -317,14 +315,9 @@ static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) > * dereference. > */ > armpmu = *(void **)dev; > - plat_device = armpmu->plat_device; > - plat = dev_get_platdata(&plat_device->dev); > > start_clock = sched_clock(); > - if (plat && plat->handle_irq) > - ret = plat->handle_irq(irq, armpmu, armpmu->handle_irq); > - else > - ret = armpmu->handle_irq(irq, armpmu); > + ret = armpmu->handle_irq(irq, armpmu); > finish_clock = sched_clock(); > > perf_sample_event_took(finish_clock - start_clock); It's nice to see the plat stuff disappearing! > diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c > index 61b53c46edfa..d5bbd79abd4c 100644 > --- a/arch/arm/kernel/perf_event_cpu.c > +++ b/arch/arm/kernel/perf_event_cpu.c > @@ -59,6 +59,116 @@ int perf_num_counters(void) > } > EXPORT_SYMBOL_GPL(perf_num_counters); > > +#ifdef CONFIG_SMP > + > +static cpumask_t down_prepare_cpu_mask; > +static DEFINE_SPINLOCK(down_prepare_cpu_lock); I think the names here are a little misleading, because we care about the whole window from CPU_DOWN_PREPARE to CPU_DEAD (or DOWN_FAILED). I think these would be clearer with s/down_prepare_cpu/dying_cpu/ (though admittedly that could also be confused with CPU_DYING). > + > +/* > + * Workaround logic that is distributed to all cores if the PMU has only > + * a single IRQ and the CPU receiving that IRQ cannot handle it. Its > + * job is to try to service the interrupt on the current CPU. It will > + * also enable the IRQ again if all the other CPUs have already tried to > + * service it. > + */ > +static void cpu_pmu_do_percpu_work(struct irq_work *w) Perhaps do_muxed_irq_work? > +{ > + struct pmu_hw_events *hw_events = > + container_of(w, struct pmu_hw_events, work); > + struct arm_pmu *cpu_pmu = hw_events->percpu_pmu; > + > + /* Ignore the return code, we can do nothing useful with it */ > + (void) cpu_pmu->handle_irq(0, cpu_pmu); Nit: no space after a cast please. Do we need the void cast here? Does your toolchain complain? > + > + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) > + enable_irq(cpu_pmu->muxed_spi_workaround_irq); I'm a little uneasy about calling enable_irq here, given we're in IRQ context. While it doesn't look we'd be wired up through an irqchip with irq_bus_lock or irq_bus_sync_unlock, I'm not sure how safe it is to rely on that being the only thing that matters. It would be nice to hear from someone familiar with the IRQ code on that respect. > +} > + > +/* > + * Workaround for systems where all PMU interrupts are targeting a > + * single SPI. > + * > + * The workaround will disable the interrupt and distribute irqwork to all > + * the other processors in the system. Hopefully one of them will clear the > + * interrupt... > + * > + * The workaround is only deployed when all PMU interrupts are aimed > + * at a single core. As a result the workaround is never re-entered > + * making it safe for us to use static data to maintain state. > + */ > +static void cpu_pmu_deploy_muxed_spi_workaround(struct arm_pmu *cpu_pmu) Perhaps distribute_muxed_irq? > +{ > + static cpumask_t irqwork_mask; > + int cpu; > + > + disable_irq_nosync(cpu_pmu->muxed_spi_workaround_irq); > + spin_lock(&down_prepare_cpu_lock); > + > + /* > + * Combining cpu_online_mask and down_prepare_cpu_mask gives > + * us the CPUs that are currently online and cannot die until > + * we release down_prepare_cpu_lock. > + */ > + cpumask_andnot(&irqwork_mask, cpu_online_mask, &down_prepare_cpu_mask); > + cpumask_clear_cpu(smp_processor_id(), &irqwork_mask); > + atomic_add(cpumask_weight(&irqwork_mask), &cpu_pmu->remaining_irq_work); > + > + for_each_cpu(cpu, &irqwork_mask) { > + struct pmu_hw_events *hw_events = > + per_cpu_ptr(cpu_pmu->hw_events, cpu); > + > + if (!irq_work_queue_on(&hw_events->work, cpu)) > + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) > + enable_irq(cpu_pmu->muxed_spi_workaround_irq); > + } > + > + spin_unlock(&down_prepare_cpu_lock); > +} I think this works, given the notifier logic and hotplug_cfd flushing any pending irq_work items. > + > +/* > + * Called when the main interrupt handler cannot determine the source > + * of interrupt. It will deploy a workaround if we are running on an SMP > + * platform with only a single muxed SPI. > + */ > +static irqreturn_t cpu_pmu_handle_irq_none(int irq_num, struct arm_pmu *cpu_pmu) > +{ > + if (irq_num != cpu_pmu->muxed_spi_workaround_irq) > + return IRQ_NONE; This is somewhat opaque. I'd rather just have a flag to determine when we need to do any special handling for the muxed case (or better, swizzle the irq handler to a wrapper that pings the other CPUs and calls the usual handler). [...] > +static int cpu_pmu_muxed_spi_workaround_init(struct arm_pmu *cpu_pmu) > +{ > + struct platform_device *pmu_device = cpu_pmu->plat_device; > + > + atomic_set(&cpu_pmu->remaining_irq_work, 0); Then we can move this atomic_set into the usual init path for SMP and get rid of these init/term functions. [...] > diff --git a/arch/arm/kernel/perf_event_v7.c b/arch/arm/kernel/perf_event_v7.c > index 8993770c47de..0dd914c10803 100644 > --- a/arch/arm/kernel/perf_event_v7.c > +++ b/arch/arm/kernel/perf_event_v7.c > @@ -792,7 +792,7 @@ static irqreturn_t armv7pmu_handle_irq(int irq_num, void *dev) > * Did an overflow occur? > */ > if (!armv7_pmnc_has_overflowed(pmnc)) > - return IRQ_NONE; > + return cpu_pmu_handle_irq_none(irq_num, cpu_pmu); Won't this leave samples skewed towards the CPU the interrupt is affine to? If you're counting something like cycles with a short enough period (and therefore effectively always have something to handle on the local CPU), we might never ping the other CPUs. I think we always need to ping the other CPUs, regardless of whether there was something to handle on this CPU. Thanks, Mark.
On 31/03/15 18:08, Mark Rutland wrote: > Hi Daniel, > > I'd very much like to see us converge on a solution for this soon. The > existing hack is getting in the way of other rework of the arm/arm64 > perf code. I'd quite like to see this patch sorted out too (mostly because one o my "go to" devices still crashes horribly whenever I try to do any profiling on a mainline kernel). > I think the approach this patch takes should work, but there are some > parts that can be cleaned up (hopefully mostly cosmetic). Unfortunately > I don't seem to have a relevant platform for testing on. > > [...] > >> diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h >> index b1596bd59129..dfef7904b790 100644 >> --- a/arch/arm/include/asm/pmu.h >> +++ b/arch/arm/include/asm/pmu.h >> @@ -87,6 +87,14 @@ struct pmu_hw_events { >> * already have to allocate this struct per cpu. >> */ >> struct arm_pmu *percpu_pmu; >> + >> +#ifdef CONFIG_SMP >> + /* >> + * This is used to schedule workaround logic on platforms where all >> + * the PMUs are attached to a single SPI. >> + */ >> + struct irq_work work; >> +#endif >> }; >> >> struct arm_pmu { >> @@ -117,6 +125,10 @@ struct arm_pmu { >> struct platform_device *plat_device; >> struct pmu_hw_events __percpu *hw_events; >> struct notifier_block hotplug_nb; >> +#ifdef CONFIG_SMP >> + int muxed_spi_workaround_irq; > > There's nothing workaround specific about this IRQ; it's just the only > IRQ. > > I think we should just pre-parse all the IRQs into a list at probe time, > regardless of SMP or the workaround. Then we can just grab the first > (and only) interrupt from the list in the workaround paths, and > otherwise just iterate over the list. What other uses do you anticipate for such a list? I don't really understand why we would create a list when we only ever consume the first entry. If there is a use for such information then why keep it as a list. Wouldn't the code be simpler if we add it as a field in the percpu data structure? For PPIs all values would be the same, for SPIs all different, for broken SoCs all after [0] would be 0. >> + atomic_t remaining_irq_work; > > Perhaps remaining_work_irqs? That would make it clear that this is a > counter rather than a boolean or enumeration. We could s/work/fake/ or > something to that effect. I guess the thing we are actually counting is CPUs so remaining_cpus_with_irq_work would therefore be extremely descriptive. >> @@ -317,14 +315,9 @@ static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) >> * dereference. >> */ >> armpmu = *(void **)dev; >> - plat_device = armpmu->plat_device; >> - plat = dev_get_platdata(&plat_device->dev); >> >> start_clock = sched_clock(); >> - if (plat && plat->handle_irq) >> - ret = plat->handle_irq(irq, armpmu, armpmu->handle_irq); >> - else >> - ret = armpmu->handle_irq(irq, armpmu); >> + ret = armpmu->handle_irq(irq, armpmu); >> finish_clock = sched_clock(); >> >> perf_sample_event_took(finish_clock - start_clock); > > It's nice to see the plat stuff disappearing! > >> diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c >> index 61b53c46edfa..d5bbd79abd4c 100644 >> --- a/arch/arm/kernel/perf_event_cpu.c >> +++ b/arch/arm/kernel/perf_event_cpu.c >> @@ -59,6 +59,116 @@ int perf_num_counters(void) >> } >> EXPORT_SYMBOL_GPL(perf_num_counters); >> >> +#ifdef CONFIG_SMP >> + >> +static cpumask_t down_prepare_cpu_mask; >> +static DEFINE_SPINLOCK(down_prepare_cpu_lock); > > I think the names here are a little misleading, because we care about > the whole window from CPU_DOWN_PREPARE to CPU_DEAD (or DOWN_FAILED). I > think these would be clearer with s/down_prepare_cpu/dying_cpu/ (though > admittedly that could also be confused with CPU_DYING). Fine. I'll change this. >> + >> +/* >> + * Workaround logic that is distributed to all cores if the PMU has only >> + * a single IRQ and the CPU receiving that IRQ cannot handle it. Its >> + * job is to try to service the interrupt on the current CPU. It will >> + * also enable the IRQ again if all the other CPUs have already tried to >> + * service it. >> + */ >> +static void cpu_pmu_do_percpu_work(struct irq_work *w) > > Perhaps do_muxed_irq_work? Ok. >> +{ >> + struct pmu_hw_events *hw_events = >> + container_of(w, struct pmu_hw_events, work); >> + struct arm_pmu *cpu_pmu = hw_events->percpu_pmu; >> + >> + /* Ignore the return code, we can do nothing useful with it */ >> + (void) cpu_pmu->handle_irq(0, cpu_pmu); > > Nit: no space after a cast please. > > Do we need the void cast here? Does your toolchain complain? I've always considered casting to void to be an executable comment... In this case I added it out of habit rather than because the toolchain complained. >> + >> + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) >> + enable_irq(cpu_pmu->muxed_spi_workaround_irq); > > I'm a little uneasy about calling enable_irq here, given we're in IRQ > context. While it doesn't look we'd be wired up through an irqchip with > irq_bus_lock or irq_bus_sync_unlock, I'm not sure how safe it is to rely > on that being the only thing that matters. > > It would be nice to hear from someone familiar with the IRQ code on that > respect. Sure. I've reviewed this as far as I can. Probably the most significant difference between enable and disable paths is the retrigger logic. I can't see anything there that would cause a problem. >> +} >> + >> +/* >> + * Workaround for systems where all PMU interrupts are targeting a >> + * single SPI. >> + * >> + * The workaround will disable the interrupt and distribute irqwork to all >> + * the other processors in the system. Hopefully one of them will clear the >> + * interrupt... >> + * >> + * The workaround is only deployed when all PMU interrupts are aimed >> + * at a single core. As a result the workaround is never re-entered >> + * making it safe for us to use static data to maintain state. >> + */ >> +static void cpu_pmu_deploy_muxed_spi_workaround(struct arm_pmu *cpu_pmu) > > Perhaps distribute_muxed_irq? Could do. Personally I prefer to be clear that this is deploying a workaround (i.e. implying it does something odd on a small number of SoCs) rather than this code being part of the normal case. >> +{ >> + static cpumask_t irqwork_mask; >> + int cpu; >> + >> + disable_irq_nosync(cpu_pmu->muxed_spi_workaround_irq); >> + spin_lock(&down_prepare_cpu_lock); >> + >> + /* >> + * Combining cpu_online_mask and down_prepare_cpu_mask gives >> + * us the CPUs that are currently online and cannot die until >> + * we release down_prepare_cpu_lock. >> + */ >> + cpumask_andnot(&irqwork_mask, cpu_online_mask, &down_prepare_cpu_mask); >> + cpumask_clear_cpu(smp_processor_id(), &irqwork_mask); >> + atomic_add(cpumask_weight(&irqwork_mask), &cpu_pmu->remaining_irq_work); >> + >> + for_each_cpu(cpu, &irqwork_mask) { >> + struct pmu_hw_events *hw_events = >> + per_cpu_ptr(cpu_pmu->hw_events, cpu); >> + >> + if (!irq_work_queue_on(&hw_events->work, cpu)) >> + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) >> + enable_irq(cpu_pmu->muxed_spi_workaround_irq); >> + } >> + >> + spin_unlock(&down_prepare_cpu_lock); >> +} > > I think this works, given the notifier logic and hotplug_cfd flushing > any pending irq_work items. Certainly its a lot better than the benign race thing I was trying to do before! >> + >> +/* >> + * Called when the main interrupt handler cannot determine the source >> + * of interrupt. It will deploy a workaround if we are running on an SMP >> + * platform with only a single muxed SPI. >> + */ >> +static irqreturn_t cpu_pmu_handle_irq_none(int irq_num, struct arm_pmu *cpu_pmu) >> +{ >> + if (irq_num != cpu_pmu->muxed_spi_workaround_irq) >> + return IRQ_NONE; > > This is somewhat opaque. > > I'd rather just have a flag to determine when we need to do any special > handling for the muxed case (or better, swizzle the irq handler to a > wrapper that pings the other CPUs and calls the usual handler). Using a different handler for the workaround makes sense. IIRC I avoided that previously because the way the code is currently split between perf_event.c and perf_event_cpu.c didn't make that very natural. I'll look at this again. > [...] > >> +static int cpu_pmu_muxed_spi_workaround_init(struct arm_pmu *cpu_pmu) >> +{ >> + struct platform_device *pmu_device = cpu_pmu->plat_device; >> + >> + atomic_set(&cpu_pmu->remaining_irq_work, 0); > > Then we can move this atomic_set into the usual init path for SMP and > get rid of these init/term functions. Ok. > [...] > >> diff --git a/arch/arm/kernel/perf_event_v7.c b/arch/arm/kernel/perf_event_v7.c >> index 8993770c47de..0dd914c10803 100644 >> --- a/arch/arm/kernel/perf_event_v7.c >> +++ b/arch/arm/kernel/perf_event_v7.c >> @@ -792,7 +792,7 @@ static irqreturn_t armv7pmu_handle_irq(int irq_num, void *dev) >> * Did an overflow occur? >> */ >> if (!armv7_pmnc_has_overflowed(pmnc)) >> - return IRQ_NONE; >> + return cpu_pmu_handle_irq_none(irq_num, cpu_pmu); > > Won't this leave samples skewed towards the CPU the interrupt is affine > to? If you're counting something like cycles with a short enough period > (and therefore effectively always have something to handle on the local > CPU), we might never ping the other CPUs. Do we really care about fidelity of results when servicing a perf interrupt causes another perf interrupt to happen ;-) ? At this point perf has already stopped profiling anything useful. > I think we always need to ping the other CPUs, regardless of whether > there was something to handle on this CPU. Ok. If we make this unconditional then we can, as you suggest above somewhere, redistribute the interrupt before trying to handle it. The faster we can interrupt the other CPUs the higher the fidelity of the profile (less time for PC to change between perf event triggering and CPU reacting). Daniel.
On 31/03/15 17:20, Will Deacon wrote: > Hi Daniel, > > On Wed, Mar 04, 2015 at 01:25:45PM +0000, Daniel Thompson wrote: >> Some ARM platforms mux the PMU interrupt of every core into a single >> SPI. On such platforms if the PMU of any core except 0 raises an interrupt >> then it cannot be serviced and eventually, if you are lucky, the spurious >> irq detection might forcefully disable the interrupt. >> >> On these SoCs it is not possible to determine which core raised the >> interrupt so workaround this issue by queuing irqwork on the other >> cores whenever the primary interrupt handler is unable to service the >> interrupt. >> >> The u8500 platform has an alternative workaround that dynamically alters >> the affinity of the PMU interrupt. This workaround logic is no longer >> required so the original code is removed as is the hook it relied upon. >> >> Tested on imx6q (which has fours cores/PMUs all muxed to a single SPI) >> using a simple soak, combined perf and CPU hotplug soak and using >> perf fuzzer's fast_repro.sh. > > [...] > >> diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h >> index b1596bd59129..dfef7904b790 100644 >> --- a/arch/arm/include/asm/pmu.h >> +++ b/arch/arm/include/asm/pmu.h >> @@ -87,6 +87,14 @@ struct pmu_hw_events { >> * already have to allocate this struct per cpu. >> */ >> struct arm_pmu *percpu_pmu; >> + >> +#ifdef CONFIG_SMP >> + /* >> + * This is used to schedule workaround logic on platforms where all >> + * the PMUs are attached to a single SPI. >> + */ >> + struct irq_work work; >> +#endif >> }; >> >> struct arm_pmu { >> @@ -117,6 +125,10 @@ struct arm_pmu { >> struct platform_device *plat_device; >> struct pmu_hw_events __percpu *hw_events; >> struct notifier_block hotplug_nb; >> +#ifdef CONFIG_SMP >> + int muxed_spi_workaround_irq; >> + atomic_t remaining_irq_work; >> +#endif >> }; >> >> #define to_arm_pmu(p) (container_of(p, struct arm_pmu, pmu)) >> diff --git a/arch/arm/kernel/perf_event.c b/arch/arm/kernel/perf_event.c >> index 557e128e4df0..e3fc1a0ce969 100644 >> --- a/arch/arm/kernel/perf_event.c >> +++ b/arch/arm/kernel/perf_event.c >> @@ -305,8 +305,6 @@ validate_group(struct perf_event *event) >> static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) >> { >> struct arm_pmu *armpmu; >> - struct platform_device *plat_device; >> - struct arm_pmu_platdata *plat; >> int ret; >> u64 start_clock, finish_clock; >> >> @@ -317,14 +315,9 @@ static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) >> * dereference. >> */ >> armpmu = *(void **)dev; >> - plat_device = armpmu->plat_device; >> - plat = dev_get_platdata(&plat_device->dev); >> >> start_clock = sched_clock(); >> - if (plat && plat->handle_irq) >> - ret = plat->handle_irq(irq, armpmu, armpmu->handle_irq); >> - else >> - ret = armpmu->handle_irq(irq, armpmu); >> + ret = armpmu->handle_irq(irq, armpmu); >> finish_clock = sched_clock(); >> >> perf_sample_event_took(finish_clock - start_clock); >> diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c >> index 61b53c46edfa..d5bbd79abd4c 100644 >> --- a/arch/arm/kernel/perf_event_cpu.c >> +++ b/arch/arm/kernel/perf_event_cpu.c >> @@ -59,6 +59,116 @@ int perf_num_counters(void) >> } >> EXPORT_SYMBOL_GPL(perf_num_counters); >> >> +#ifdef CONFIG_SMP >> + >> +static cpumask_t down_prepare_cpu_mask; >> +static DEFINE_SPINLOCK(down_prepare_cpu_lock); >> + >> +/* >> + * Workaround logic that is distributed to all cores if the PMU has only >> + * a single IRQ and the CPU receiving that IRQ cannot handle it. Its >> + * job is to try to service the interrupt on the current CPU. It will >> + * also enable the IRQ again if all the other CPUs have already tried to >> + * service it. >> + */ >> +static void cpu_pmu_do_percpu_work(struct irq_work *w) >> +{ >> + struct pmu_hw_events *hw_events = >> + container_of(w, struct pmu_hw_events, work); >> + struct arm_pmu *cpu_pmu = hw_events->percpu_pmu; >> + >> + /* Ignore the return code, we can do nothing useful with it */ >> + (void) cpu_pmu->handle_irq(0, cpu_pmu); >> + >> + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) >> + enable_irq(cpu_pmu->muxed_spi_workaround_irq); >> +} >> + >> +/* >> + * Workaround for systems where all PMU interrupts are targeting a >> + * single SPI. >> + * >> + * The workaround will disable the interrupt and distribute irqwork to all >> + * the other processors in the system. Hopefully one of them will clear the >> + * interrupt... >> + * >> + * The workaround is only deployed when all PMU interrupts are aimed >> + * at a single core. As a result the workaround is never re-entered >> + * making it safe for us to use static data to maintain state. >> + */ >> +static void cpu_pmu_deploy_muxed_spi_workaround(struct arm_pmu *cpu_pmu) >> +{ >> + static cpumask_t irqwork_mask; >> + int cpu; >> + >> + disable_irq_nosync(cpu_pmu->muxed_spi_workaround_irq); >> + spin_lock(&down_prepare_cpu_lock); >> + >> + /* >> + * Combining cpu_online_mask and down_prepare_cpu_mask gives >> + * us the CPUs that are currently online and cannot die until >> + * we release down_prepare_cpu_lock. >> + */ >> + cpumask_andnot(&irqwork_mask, cpu_online_mask, &down_prepare_cpu_mask); >> + cpumask_clear_cpu(smp_processor_id(), &irqwork_mask); >> + atomic_add(cpumask_weight(&irqwork_mask), &cpu_pmu->remaining_irq_work); > > AFAICT, this is a hack to avoid get_online_cpus (which can sleep) from irq > context? Is there no way we can do try_get_online_cpus, and just return > IRQ_NONE if that fails? At some point, the hotplug operation will complete > and we'll be able to service the pending interrupt. I think that would allow > us to kill the down_prepare_cpu_lock. It certainly doesn't look easy but I will take a closer look... From the perf side its reasonably easy. I don't think we can return IRQ_NONE (we might own the h.p. lock on the CPU handling the interrupt) so we have to disable the interrupt. However we could probably arrange to re-enable it from the hotplug notifications when this is needed. Unfortunately I'm not sure the cpu_hotplug side is so easy.
> >> struct arm_pmu { > >> @@ -117,6 +125,10 @@ struct arm_pmu { > >> struct platform_device *plat_device; > >> struct pmu_hw_events __percpu *hw_events; > >> struct notifier_block hotplug_nb; > >> +#ifdef CONFIG_SMP > >> + int muxed_spi_workaround_irq; > > > > There's nothing workaround specific about this IRQ; it's just the only > > IRQ. > > > > I think we should just pre-parse all the IRQs into a list at probe time, > > regardless of SMP or the workaround. Then we can just grab the first > > (and only) interrupt from the list in the workaround paths, and > > otherwise just iterate over the list. > > What other uses do you anticipate for such a list? I don't really > understand why we would create a list when we only ever consume the > first entry. It would go parallel to the affinity property Will recently added, and would allow us to separate the DT parsing from the request/free paths, making those far easier to understand (and likely a little faster too). > If there is a use for such information then why keep it as a list. > Wouldn't the code be simpler if we add it as a field in the percpu data > structure? > > For PPIs all values would be the same, for SPIs all different, for > broken SoCs all after [0] would be 0. That's a nice idea. That would make the affinity info implicit, and could be far neater. > >> + atomic_t remaining_irq_work; > > > > Perhaps remaining_work_irqs? That would make it clear that this is a > > counter rather than a boolean or enumeration. We could s/work/fake/ or > > something to that effect. > > I guess the thing we are actually counting is CPUs so > remaining_cpus_with_irq_work would therefore be extremely descriptive. It would be nice if we could come up with something that was a little more concise. Perhaps cpus_with_work would be good enough? > >> +} > >> + > >> +/* > >> + * Workaround for systems where all PMU interrupts are targeting a > >> + * single SPI. > >> + * > >> + * The workaround will disable the interrupt and distribute irqwork to all > >> + * the other processors in the system. Hopefully one of them will clear the > >> + * interrupt... > >> + * > >> + * The workaround is only deployed when all PMU interrupts are aimed > >> + * at a single core. As a result the workaround is never re-entered > >> + * making it safe for us to use static data to maintain state. > >> + */ > >> +static void cpu_pmu_deploy_muxed_spi_workaround(struct arm_pmu *cpu_pmu) > > > > Perhaps distribute_muxed_irq? > > Could do. Personally I prefer to be clear that this is deploying a > workaround (i.e. implying it does something odd on a small number of > SoCs) rather than this code being part of the normal case. I'd prefer the more succinct name. We already have the comment stating that this is a workaround. [...] > >> +/* > >> + * Called when the main interrupt handler cannot determine the source > >> + * of interrupt. It will deploy a workaround if we are running on an SMP > >> + * platform with only a single muxed SPI. > >> + */ > >> +static irqreturn_t cpu_pmu_handle_irq_none(int irq_num, struct arm_pmu *cpu_pmu) > >> +{ > >> + if (irq_num != cpu_pmu->muxed_spi_workaround_irq) > >> + return IRQ_NONE; > > > > This is somewhat opaque. > > > > I'd rather just have a flag to determine when we need to do any special > > handling for the muxed case (or better, swizzle the irq handler to a > > wrapper that pings the other CPUs and calls the usual handler). > > Using a different handler for the workaround makes sense. > > IIRC I avoided that previously because the way the code is currently > split between perf_event.c and perf_event_cpu.c didn't make that very > natural. > > I'll look at this again. The split between the two is an unfortunate legacy from when it looked like system PMUs could reuse the code. We recently decoupled the CCI PMU from arm_pmu so that we could fuse the two layers and get rid of a load of indirection. I have some patches doing that. I'll try to rework them next week given it sounds like they could be a useful base for this. > > [...] > > > >> diff --git a/arch/arm/kernel/perf_event_v7.c b/arch/arm/kernel/perf_event_v7.c > >> index 8993770c47de..0dd914c10803 100644 > >> --- a/arch/arm/kernel/perf_event_v7.c > >> +++ b/arch/arm/kernel/perf_event_v7.c > >> @@ -792,7 +792,7 @@ static irqreturn_t armv7pmu_handle_irq(int irq_num, void *dev) > >> * Did an overflow occur? > >> */ > >> if (!armv7_pmnc_has_overflowed(pmnc)) > >> - return IRQ_NONE; > >> + return cpu_pmu_handle_irq_none(irq_num, cpu_pmu); > > > > Won't this leave samples skewed towards the CPU the interrupt is affine > > to? If you're counting something like cycles with a short enough period > > (and therefore effectively always have something to handle on the local > > CPU), we might never ping the other CPUs. > > Do we really care about fidelity of results when servicing a perf > interrupt causes another perf interrupt to happen ;-) ? At this point > perf has already stopped profiling anything useful. Fair point. I'll have to consider that for a bit... > > I think we always need to ping the other CPUs, regardless of whether > > there was something to handle on this CPU. > > Ok. > > If we make this unconditional then we can, as you suggest above > somewhere, redistribute the interrupt before trying to handle it. The > faster we can interrupt the other CPUs the higher the fidelity of the > profile (less time for PC to change between perf event triggering and > CPU reacting). Yup! Mark.
diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h index b1596bd59129..dfef7904b790 100644 --- a/arch/arm/include/asm/pmu.h +++ b/arch/arm/include/asm/pmu.h @@ -87,6 +87,14 @@ struct pmu_hw_events { * already have to allocate this struct per cpu. */ struct arm_pmu *percpu_pmu; + +#ifdef CONFIG_SMP + /* + * This is used to schedule workaround logic on platforms where all + * the PMUs are attached to a single SPI. + */ + struct irq_work work; +#endif }; struct arm_pmu { @@ -117,6 +125,10 @@ struct arm_pmu { struct platform_device *plat_device; struct pmu_hw_events __percpu *hw_events; struct notifier_block hotplug_nb; +#ifdef CONFIG_SMP + int muxed_spi_workaround_irq; + atomic_t remaining_irq_work; +#endif }; #define to_arm_pmu(p) (container_of(p, struct arm_pmu, pmu)) diff --git a/arch/arm/kernel/perf_event.c b/arch/arm/kernel/perf_event.c index 557e128e4df0..e3fc1a0ce969 100644 --- a/arch/arm/kernel/perf_event.c +++ b/arch/arm/kernel/perf_event.c @@ -305,8 +305,6 @@ validate_group(struct perf_event *event) static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) { struct arm_pmu *armpmu; - struct platform_device *plat_device; - struct arm_pmu_platdata *plat; int ret; u64 start_clock, finish_clock; @@ -317,14 +315,9 @@ static irqreturn_t armpmu_dispatch_irq(int irq, void *dev) * dereference. */ armpmu = *(void **)dev; - plat_device = armpmu->plat_device; - plat = dev_get_platdata(&plat_device->dev); start_clock = sched_clock(); - if (plat && plat->handle_irq) - ret = plat->handle_irq(irq, armpmu, armpmu->handle_irq); - else - ret = armpmu->handle_irq(irq, armpmu); + ret = armpmu->handle_irq(irq, armpmu); finish_clock = sched_clock(); perf_sample_event_took(finish_clock - start_clock); diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c index 61b53c46edfa..d5bbd79abd4c 100644 --- a/arch/arm/kernel/perf_event_cpu.c +++ b/arch/arm/kernel/perf_event_cpu.c @@ -59,6 +59,116 @@ int perf_num_counters(void) } EXPORT_SYMBOL_GPL(perf_num_counters); +#ifdef CONFIG_SMP + +static cpumask_t down_prepare_cpu_mask; +static DEFINE_SPINLOCK(down_prepare_cpu_lock); + +/* + * Workaround logic that is distributed to all cores if the PMU has only + * a single IRQ and the CPU receiving that IRQ cannot handle it. Its + * job is to try to service the interrupt on the current CPU. It will + * also enable the IRQ again if all the other CPUs have already tried to + * service it. + */ +static void cpu_pmu_do_percpu_work(struct irq_work *w) +{ + struct pmu_hw_events *hw_events = + container_of(w, struct pmu_hw_events, work); + struct arm_pmu *cpu_pmu = hw_events->percpu_pmu; + + /* Ignore the return code, we can do nothing useful with it */ + (void) cpu_pmu->handle_irq(0, cpu_pmu); + + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) + enable_irq(cpu_pmu->muxed_spi_workaround_irq); +} + +/* + * Workaround for systems where all PMU interrupts are targeting a + * single SPI. + * + * The workaround will disable the interrupt and distribute irqwork to all + * the other processors in the system. Hopefully one of them will clear the + * interrupt... + * + * The workaround is only deployed when all PMU interrupts are aimed + * at a single core. As a result the workaround is never re-entered + * making it safe for us to use static data to maintain state. + */ +static void cpu_pmu_deploy_muxed_spi_workaround(struct arm_pmu *cpu_pmu) +{ + static cpumask_t irqwork_mask; + int cpu; + + disable_irq_nosync(cpu_pmu->muxed_spi_workaround_irq); + spin_lock(&down_prepare_cpu_lock); + + /* + * Combining cpu_online_mask and down_prepare_cpu_mask gives + * us the CPUs that are currently online and cannot die until + * we release down_prepare_cpu_lock. + */ + cpumask_andnot(&irqwork_mask, cpu_online_mask, &down_prepare_cpu_mask); + cpumask_clear_cpu(smp_processor_id(), &irqwork_mask); + atomic_add(cpumask_weight(&irqwork_mask), &cpu_pmu->remaining_irq_work); + + for_each_cpu(cpu, &irqwork_mask) { + struct pmu_hw_events *hw_events = + per_cpu_ptr(cpu_pmu->hw_events, cpu); + + if (!irq_work_queue_on(&hw_events->work, cpu)) + if (atomic_dec_and_test(&cpu_pmu->remaining_irq_work)) + enable_irq(cpu_pmu->muxed_spi_workaround_irq); + } + + spin_unlock(&down_prepare_cpu_lock); +} + +/* + * Called when the main interrupt handler cannot determine the source + * of interrupt. It will deploy a workaround if we are running on an SMP + * platform with only a single muxed SPI. + */ +static irqreturn_t cpu_pmu_handle_irq_none(int irq_num, struct arm_pmu *cpu_pmu) +{ + if (irq_num != cpu_pmu->muxed_spi_workaround_irq) + return IRQ_NONE; + + cpu_pmu_deploy_muxed_spi_workaround(cpu_pmu); + return IRQ_HANDLED; +} + +static int cpu_pmu_muxed_spi_workaround_init(struct arm_pmu *cpu_pmu) +{ + struct platform_device *pmu_device = cpu_pmu->plat_device; + + atomic_set(&cpu_pmu->remaining_irq_work, 0); + cpu_pmu->muxed_spi_workaround_irq = platform_get_irq(pmu_device, 0); + + return 0; +} + +static void cpu_pmu_muxed_spi_workaround_term(struct arm_pmu *cpu_pmu) +{ + cpu_pmu->muxed_spi_workaround_irq = 0; +} +#else /* CONFIG_SMP */ +static int cpu_pmu_muxed_spi_workaround_init(struct arm_pmu *cpu_pmu) +{ + return 0; +} + +static void cpu_pmu_muxed_spi_workaround_term(struct arm_pmu *cpu_pmu) +{ +} + +static irqreturn_t cpu_pmu_handle_irq_none(int irq_num, struct arm_pmu *cpu_pmu) +{ + return IRQ_NONE; +} +#endif /* CONFIG_SMP */ + /* Include the PMU-specific implementations. */ #include "perf_event_xscale.c" #include "perf_event_v6.c" @@ -98,6 +208,8 @@ static void cpu_pmu_free_irq(struct arm_pmu *cpu_pmu) if (irq >= 0) free_irq(irq, per_cpu_ptr(&hw_events->percpu_pmu, i)); } + + cpu_pmu_muxed_spi_workaround_term(cpu_pmu); } } @@ -155,31 +267,65 @@ static int cpu_pmu_request_irq(struct arm_pmu *cpu_pmu, irq_handler_t handler) cpumask_set_cpu(i, &cpu_pmu->active_irqs); } + + /* + * If we are running SMP and have only one interrupt source + * then get ready to share that single irq among the cores. + */ + if (nr_cpu_ids > 1 && irqs == 1) { + err = cpu_pmu_muxed_spi_workaround_init(cpu_pmu); + if (err) + return err; + } } return 0; } -/* - * PMU hardware loses all context when a CPU goes offline. - * When a CPU is hotplugged back in, since some hardware registers are - * UNKNOWN at reset, the PMU must be explicitly reset to avoid reading - * junk values out of them. - */ static int cpu_pmu_notify(struct notifier_block *b, unsigned long action, void *hcpu) { struct arm_pmu *pmu = container_of(b, struct arm_pmu, hotplug_nb); + long cpu = (long)hcpu; + unsigned long flags; + + switch (action & ~CPU_TASKS_FROZEN) { + /* + * PMU hardware loses all context when a CPU goes offline. + * When a CPU is hotplugged back in, since some hardware registers are + * UNKNOWN at reset, the PMU must be explicitly reset to avoid reading + * junk values out of them. + */ + case CPU_STARTING: + if (pmu->reset) + pmu->reset(pmu); + else + return NOTIFY_DONE; + + return NOTIFY_OK; + +#ifdef CONFIG_SMP + /* + * The workaround logic in cpu_pmu_handle_irq_none requires us + * to keep track of CPUs that may be about to die so we can + * avoid sending them irqwork. + */ + case CPU_DOWN_PREPARE: + spin_lock_irqsave(&down_prepare_cpu_lock, flags); + cpumask_set_cpu(cpu, &down_prepare_cpu_mask); + spin_unlock_irqrestore(&down_prepare_cpu_lock, flags); + return NOTIFY_OK; + + case CPU_DOWN_FAILED: + case CPU_DEAD: + spin_lock_irqsave(&down_prepare_cpu_lock, flags); + cpumask_clear_cpu(cpu, &down_prepare_cpu_mask); + spin_unlock_irqrestore(&down_prepare_cpu_lock, flags); + return NOTIFY_OK; +#endif + } - if ((action & ~CPU_TASKS_FROZEN) != CPU_STARTING) - return NOTIFY_DONE; - - if (pmu->reset) - pmu->reset(pmu); - else - return NOTIFY_DONE; - - return NOTIFY_OK; + return NOTIFY_DONE; } static int cpu_pmu_init(struct arm_pmu *cpu_pmu) @@ -201,6 +347,9 @@ static int cpu_pmu_init(struct arm_pmu *cpu_pmu) struct pmu_hw_events *events = per_cpu_ptr(cpu_hw_events, cpu); raw_spin_lock_init(&events->pmu_lock); events->percpu_pmu = cpu_pmu; +#ifdef CONFIG_SMP + init_irq_work(&events->work, cpu_pmu_do_percpu_work); +#endif } cpu_pmu->hw_events = cpu_hw_events; diff --git a/arch/arm/kernel/perf_event_v7.c b/arch/arm/kernel/perf_event_v7.c index 8993770c47de..0dd914c10803 100644 --- a/arch/arm/kernel/perf_event_v7.c +++ b/arch/arm/kernel/perf_event_v7.c @@ -792,7 +792,7 @@ static irqreturn_t armv7pmu_handle_irq(int irq_num, void *dev) * Did an overflow occur? */ if (!armv7_pmnc_has_overflowed(pmnc)) - return IRQ_NONE; + return cpu_pmu_handle_irq_none(irq_num, cpu_pmu); /* * Handle the counter(s) overflow(s) diff --git a/arch/arm/mach-ux500/cpu-db8500.c b/arch/arm/mach-ux500/cpu-db8500.c index 6f63954c8bde..917774999c5c 100644 --- a/arch/arm/mach-ux500/cpu-db8500.c +++ b/arch/arm/mach-ux500/cpu-db8500.c @@ -12,8 +12,6 @@ #include <linux/init.h> #include <linux/device.h> #include <linux/amba/bus.h> -#include <linux/interrupt.h> -#include <linux/irq.h> #include <linux/platform_device.h> #include <linux/io.h> #include <linux/mfd/abx500/ab8500.h> @@ -23,7 +21,6 @@ #include <linux/regulator/machine.h> #include <linux/random.h> -#include <asm/pmu.h> #include <asm/mach/map.h> #include "setup.h" @@ -99,30 +96,6 @@ static void __init u8500_map_io(void) iotable_init(u8500_io_desc, ARRAY_SIZE(u8500_io_desc)); } -/* - * The PMU IRQ lines of two cores are wired together into a single interrupt. - * Bounce the interrupt to the other core if it's not ours. - */ -static irqreturn_t db8500_pmu_handler(int irq, void *dev, irq_handler_t handler) -{ - irqreturn_t ret = handler(irq, dev); - int other = !smp_processor_id(); - - if (ret == IRQ_NONE && cpu_online(other)) - irq_set_affinity(irq, cpumask_of(other)); - - /* - * We should be able to get away with the amount of IRQ_NONEs we give, - * while still having the spurious IRQ detection code kick in if the - * interrupt really starts hitting spuriously. - */ - return ret; -} - -static struct arm_pmu_platdata db8500_pmu_platdata = { - .handle_irq = db8500_pmu_handler, -}; - static const char *db8500_read_soc_id(void) { void __iomem *uid = __io_address(U8500_BB_UID_BASE); @@ -143,8 +116,6 @@ static struct device * __init db8500_soc_device_init(void) } static struct of_dev_auxdata u8500_auxdata_lookup[] __initdata = { - /* Requires call-back bindings. */ - OF_DEV_AUXDATA("arm,cortex-a9-pmu", 0, "arm-pmu", &db8500_pmu_platdata), /* Requires DMA bindings. */ OF_DEV_AUXDATA("stericsson,ux500-msp-i2s", 0x80123000, "ux500-msp-i2s.0", &msp0_platform_data),
Some ARM platforms mux the PMU interrupt of every core into a single SPI. On such platforms if the PMU of any core except 0 raises an interrupt then it cannot be serviced and eventually, if you are lucky, the spurious irq detection might forcefully disable the interrupt. On these SoCs it is not possible to determine which core raised the interrupt so workaround this issue by queuing irqwork on the other cores whenever the primary interrupt handler is unable to service the interrupt. The u8500 platform has an alternative workaround that dynamically alters the affinity of the PMU interrupt. This workaround logic is no longer required so the original code is removed as is the hook it relied upon. Tested on imx6q (which has fours cores/PMUs all muxed to a single SPI) using a simple soak, combined perf and CPU hotplug soak and using perf fuzzer's fast_repro.sh. Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org> --- Notes: v2 was tested on u8500 (thanks to Linus Walleij). The latest patch doesn't change the nature of the workaround itself but there has been substantial churn in the logic to decide when it can safely be deployed. Thus the changes were sufficient for me not to preserve the Tested-By:. v6: * Redesigned the code that decides if it is safe to deploy the workaround (acting on the review by Mark Rutland). Code should no longer race during hot unplug; previous patches sought to make the hot unplug race benign and the old approach had flaws and even if it could be made correct was tortuously hard to review. v5: * Removed the work queue nonsense; being completely race-free requires us to take a mutex or avoid dispatch from interrupt (Will Deacon). Replacement code can potentially race with a CPU hot unplug however it is careful to minimise exposure, to mitigate harmful effects and has fairly prominent comments. v4: * Ripped out the logic that tried to preserve the operation of the spurious interrupt detector. It was complex and not really needed (Will Deacon). * Removed a redundant memory barrier and added a comment explaining why it is not needed (Will Deacon). * Made fully safe w.r.t. hotplug by falling back to a work queue if there is a hotplug operation in flight when the PMU interrupt comes in (Will Deacon). The work queue code paths have been tested synthetically (by changing the if condition). * Posted the correct, as in compilable and tested, version of the code (Will Deacon). v3: * Removed function pointer indirection when deploying workaround code and reorganise the code accordingly (Mark Rutland). * Move the workaround state tracking into the existing percpu data structure (Mark Rutland). * Renamed cret to percpu_ret and rewrote the comment describing the purpose of this variable (Mark Rutland). * Copy the cpu_online_mask and use that to act on a consistent set of cpus throughout the workaround (Mark Rutland). * Changed "single_irq" to "muxed_spi" to more explicitly describe the problem. v2: * Fixed build problems on systems without SMP. v1: * Thanks to Lucas Stach, Russell King and Thomas Gleixner for critiquing an older, completely different way to tackle the same problem. arch/arm/include/asm/pmu.h | 12 +++ arch/arm/kernel/perf_event.c | 9 +- arch/arm/kernel/perf_event_cpu.c | 179 +++++++++++++++++++++++++++++++++++---- arch/arm/kernel/perf_event_v7.c | 2 +- arch/arm/mach-ux500/cpu-db8500.c | 29 ------- 5 files changed, 178 insertions(+), 53 deletions(-) -- 2.1.0