linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: pmu: reject duplicate PMU registrations
Date: Mon, 13 Jun 2011 10:35:55 +0100	[thread overview]
Message-ID: <1307957757-23001-3-git-send-email-mark.rutland@arm.com> (raw)
In-Reply-To: <4DEFA5E1.9010600@gmail.com>

Currently, the PMU reservation framework allows for multiple PMUs of
the same type to register themselves. This can lead to a bug with the
sequence:

register_pmu(pmu1);
reserve_pmu(pmu_type);
register_pmu(pmu2);
release_pmu(pmu1);

Here, pmu1 cannot be released, and pmu2 cannot be reserved.

This patch modifies register_pmu to reject registrations where a PMU is
already present, preventing this problem. PMUs which can have multiple
instances should not use the PMU reservation framework.

Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-By: Jamie Iles <jamie@jamieiles.com>
Acked-By: Will Deacon <will.deacon@arm.com>
---
 arch/arm/kernel/pmu.c |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/arch/arm/kernel/pmu.c b/arch/arm/kernel/pmu.c
index 87942b9..de6b1b0 100644
--- a/arch/arm/kernel/pmu.c
+++ b/arch/arm/kernel/pmu.c
@@ -34,13 +34,13 @@ static int __devinit pmu_register(struct platform_device *pdev,
 		return -EINVAL;
 	}
 
-	if (pmu_devices[type])
-		pr_warning("registering new PMU device type %d overwrites "
-				"previous registration!\n", type);
-	else
-		pr_info("registered new PMU device of type %d\n",
-				type);
+	if (pmu_devices[type]) {
+		pr_warning("rejecting duplicate registration of PMU device "
+			"type %d.", type);
+		return -ENOSPC;
+	}
 
+	pr_info("registered new PMU device of type %d\n", type);
 	pmu_devices[type] = pdev;
 	return 0;
 }
-- 
1.7.0.4

  parent reply	other threads:[~2011-06-13  9:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 14:22 [PATCH v2 0/3] DT bindings for Cortex A9 peripherals Rob Herring
2011-06-07 14:22 ` [PATCH 1/3] ARM: pmu: add OF probing support Rob Herring
2011-06-08 15:54   ` Mark Rutland
2011-06-08 16:40     ` Rob Herring
2011-06-13  9:35       ` [PATCH 0/4] ARM: pmu: improve PMU type identification Mark Rutland
2011-06-13  9:35       ` [PATCH 1/4] ARM: pmu: refactor reservation Mark Rutland
2011-06-13  9:35       ` Mark Rutland [this message]
2011-06-13  9:35       ` [PATCH 3/4] ARM: pmu: add OF probing support Mark Rutland
2011-06-13 13:40         ` Rob Herring
2011-06-13 13:48           ` Mark Rutland
2011-06-13 13:55             ` Rob Herring
2011-06-13  9:35       ` [PATCH 4/4] ARM: pmu: add platform_device_id table support Mark Rutland
2011-06-13 12:33         ` Sergei Shtylyov
2011-06-13 12:41           ` Mark Rutland
2011-06-13 14:29         ` Jamie Iles
2011-06-13 16:44       ` [PATCH 1/3] ARM: pmu: add OF probing support Grant Likely
2011-06-07 14:22 ` [PATCH 2/3] ARM: gic: add OF based initialization Rob Herring
2011-06-13 16:53   ` Grant Likely
2011-06-13 21:39     ` Rob Herring
2011-06-13 22:14     ` Russell King - ARM Linux
2011-06-14 13:56       ` Grant Likely
2011-06-07 14:22 ` [PATCH 3/3] ARM: l2x0: Add " Rob Herring
2011-06-07 16:20   ` Olof Johansson
2011-06-07 16:54     ` Rob Herring
2011-06-07 18:49       ` Olof Johansson

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=1307957757-23001-3-git-send-email-mark.rutland@arm.com \
    --to=mark.rutland@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).