From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/7] ARM: perf: register cpu_notifier at driver init
Date: Wed, 17 Oct 2012 16:33:42 +0100 [thread overview]
Message-ID: <1350488024-3224-6-git-send-email-will.deacon@arm.com> (raw)
In-Reply-To: <1350488024-3224-1-git-send-email-will.deacon@arm.com>
From: Mark Rutland <Mark.Rutland@arm.com>
The current practice of registering the cpu hotplug notifier at PMU
registration time won't be safe with multiple PMUs, as we'll repeatedly
attempt to register the notifier. This has the unfortunate effect of
silently corrupting the notifier list, leading to boot stalling.
Instead, register the notifier at init time. Its sanity checks will
prevent anything bad from happening if the notifier is called before we
have any PMUs registered.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
arch/arm/kernel/perf_event_cpu.c | 13 +++++++++++--
1 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c
index 02244fa..71c824c 100644
--- a/arch/arm/kernel/perf_event_cpu.c
+++ b/arch/arm/kernel/perf_event_cpu.c
@@ -285,7 +285,6 @@ static int __devinit cpu_pmu_device_probe(struct platform_device *pdev)
cpu_pmu = pmu;
cpu_pmu->plat_device = pdev;
cpu_pmu_init(cpu_pmu);
- register_cpu_notifier(&cpu_pmu_hotplug_notifier);
armpmu_register(cpu_pmu, cpu_pmu->name, PERF_TYPE_RAW);
return 0;
@@ -303,6 +302,16 @@ static struct platform_driver cpu_pmu_driver = {
static int __init register_pmu_driver(void)
{
- return platform_driver_register(&cpu_pmu_driver);
+ int err;
+
+ err = register_cpu_notifier(&cpu_pmu_hotplug_notifier);
+ if (err)
+ return err;
+
+ err = platform_driver_register(&cpu_pmu_driver);
+ if (err)
+ unregister_cpu_notifier(&cpu_pmu_hotplug_notifier);
+
+ return err;
}
device_initcall(register_pmu_driver);
--
1.7.4.1
next prev parent reply other threads:[~2012-10-17 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 15:33 [PATCH 0/7] ARM: perf: updates for 3.8 Will Deacon
2012-10-17 15:33 ` [PATCH 1/7] ARM: perf: add guest vs host discrimination Will Deacon
2012-10-17 15:33 ` [PATCH 2/7] ARM: perf: allocate CPU PMU dynamically at probe time Will Deacon
2012-10-17 15:33 ` [PATCH 3/7] ARM: perf: consistently use struct perf_event in arm_pmu functions Will Deacon
2012-10-17 15:33 ` [PATCH 4/7] ARM: perf: check ARMv7 counter validity on a per-pmu basis Will Deacon
2012-10-17 15:33 ` Will Deacon [this message]
2012-10-17 15:33 ` [PATCH 6/7] ARM: perf: return NOTIFY_DONE from cpu notifier when no available PMU Will Deacon
2012-10-17 15:33 ` [PATCH 7/7] ARM: perf: consistently use arm_pmu->name for PMU name Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350488024-3224-6-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).