summaryrefslogtreecommitdiffstats
path: root/arch/arm64/kernel/perf_event.c
diff options
context:
space:
mode:
authorDirk Behme2016-02-04 18:06:10 +0100
committerWill Deacon2016-02-09 12:18:39 +0100
commitc6b90653f1f7ea383734f8ce9e8df285a0c23f5b (patch)
treed9ed3415c8c573894d82331aec651d2077842ecc /arch/arm64/kernel/perf_event.c
parentARM: perf: Set ARMv7 SDER SUNIDEN bit (diff)
downloadkernel-qcow2-linux-c6b90653f1f7ea383734f8ce9e8df285a0c23f5b.tar.gz
kernel-qcow2-linux-c6b90653f1f7ea383734f8ce9e8df285a0c23f5b.tar.xz
kernel-qcow2-linux-c6b90653f1f7ea383734f8ce9e8df285a0c23f5b.zip
drivers/perf: arm_pmu: make info messages more verbose
On a big.LITTLE system e.g. with Cortex A57 and A53 in case not all cores are online at PMU probe time we might get hw perfevents: failed to probe PMU! hw perfevents: failed to register PMU devices! making it unclear which cores failed, here. Add the device tree full name which failed and the error value resulting in a more verbose and helpful message like hw perfevents: /soc/pmu_a53: failed to probe PMU! Error -6 hw perfevents: /soc/pmu_a53: failed to register PMU devices! Error -6 Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'arch/arm64/kernel/perf_event.c')
0 files changed, 0 insertions, 0 deletions