linux/drivers/perf
Robin Murphy 0d2e2a82d4 perf/arm-cci: Remove broken race mitigation
Uncore PMU drivers face an awkward cyclic dependency wherein:

 - They have to pick a valid online CPU to associate with before
   registering the PMU device, since it will get exposed to userspace
   immediately.
 - The PMU registration has to be be at least partly complete before
   hotplug events can be handled, since trying to migrate an
   uninitialised context would be bad.
 - The hotplug handler has to be ready as soon as a CPU is chosen, lest
   it go offline without the user-visible cpumask value getting updated.

The arm-cci driver has tried to solve this by using get_cpu() to pick
the current CPU and prevent it from disappearing while both
registrations are performed, but that results in taking mutexes with
preemption disabled, which makes certain configurations very unhappy:

[ 1.983337] BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:2004
[ 1.983340] in_atomic(): 1, irqs_disabled(): 0, pid: 1, name: swapper/0
[ 1.983342] Preemption disabled at:
[ 1.983353] [<ffffff80089801f4>] cci_pmu_probe+0x1dc/0x488
[ 1.983360] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.20-rt8-yocto-preempt-rt #1
[ 1.983362] Hardware name: ZynqMP ZCU102 Rev1.0 (DT)
[ 1.983364] Call trace:
[ 1.983369] dump_backtrace+0x0/0x158
[ 1.983372] show_stack+0x24/0x30
[ 1.983378] dump_stack+0x80/0xa4
[ 1.983383] ___might_sleep+0x138/0x160
[ 1.983386] __might_sleep+0x58/0x90
[ 1.983391] __rt_mutex_lock_state+0x30/0xc0
[ 1.983395] _mutex_lock+0x24/0x30
[ 1.983400] perf_pmu_register+0x2c/0x388
[ 1.983404] cci_pmu_probe+0x2bc/0x488
[ 1.983409] platform_drv_probe+0x58/0xa8

It is not feasible to resolve all the possible races outside of the perf
core itself, so address the immediate bug by following the example of
nearly every other PMU driver and not even trying to do so. Registering
the hotplug notifier first should minimise the window in which things
can go wrong, so that's about as much as we can reasonably do here. This
also revealed an additional race in assigning the global pointer too
late relative to the hotplug notifier, which gets fixed in the process.

Reported-by: Li, Meng <Meng.Li@windriver.com>
Tested-by: Corentin Labbe <clabbe.montjoie@gmail.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2019-04-23 12:29:23 +01:00
..
hisilicon For drivers that do not support context exclusion let's advertise the 2019-01-21 11:01:24 +01:00
arm_dsu_pmu.c For drivers that do not support context exclusion let's advertise the 2019-01-21 11:01:24 +01:00
arm_pmu_acpi.c arm_pmu: acpi: request IRQs up-front 2018-02-20 11:34:54 +00:00
arm_pmu_platform.c perf: Convert to using %pOFn instead of device_node.name 2018-10-01 11:33:17 +01:00
arm_pmu.c perf/core, arch/arm: Use PERF_PMU_CAP_NO_EXCLUDE conditionally 2019-01-21 11:01:22 +01:00
arm_smmuv3_pmu.c perf/smmuv3: Enable HiSilicon Erratum 162001800 quirk 2019-04-04 16:49:22 +01:00
arm_spe_pmu.c perf/aux: Make perf_event accessible to setup_aux() 2019-02-06 10:00:39 -03:00
arm-cci.c perf/arm-cci: Remove broken race mitigation 2019-04-23 12:29:23 +01:00
arm-ccn.c For drivers that do not support context exclusion let's advertise the 2019-01-21 11:01:24 +01:00
Kconfig perf/smmuv3: Add arm64 smmuv3 pmu driver 2019-04-04 16:49:21 +01:00
Makefile perf/smmuv3: Add arm64 smmuv3 pmu driver 2019-04-04 16:49:21 +01:00
qcom_l2_pmu.c perf/drivers: Strengthen exclusion checks with PERF_PMU_CAP_NO_EXCLUDE 2019-01-21 11:01:25 +01:00
qcom_l3_pmu.c perf/drivers: Strengthen exclusion checks with PERF_PMU_CAP_NO_EXCLUDE 2019-01-21 11:01:25 +01:00
thunderx2_pmu.c For drivers that do not support context exclusion let's advertise the 2019-01-21 11:01:24 +01:00
xgene_pmu.c arm64 updates for 5.1: 2019-03-10 10:17:23 -07:00