From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: perf: use raw_spinlock_t for pmu_lock
Date: Wed, 1 Dec 2010 16:35:47 +0000 [thread overview]
Message-ID: <20101201163547.GE2898@pulham.picochip.com> (raw)
In-Reply-To: <1291137443-13821-1-git-send-email-will.deacon@arm.com>
On Tue, Nov 30, 2010 at 05:17:23PM +0000, Will Deacon wrote:
> For kernels built with PREEMPT_RT, critical sections protected
> by standard spinlocks are preemptible. This is not acceptable
> on perf as (a) we may be scheduled onto a different CPU whilst
> reading/writing banked PMU registers and (b) the latency when
> reading the PMU registers becomes unpredictable.
>
> This patch upgrades the pmu_lock spinlock to a raw_spinlock
> instead.
>
> Reported-by: Jamie Iles <jamie@jamieiles.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
Hi Will,
Looks fine to me and tested on my board (not with PREEMPT_RT at the moment
though). Btw, it may be my mail reader (mutt) but trying to save your mail to
an mbox gave lots of extra characters in the patch like:
diff --git a/arch/arm/kernel/perf_event_v6.c b/arch/arm/kernel/perf_event_v=
6.c
index 3f427aa..c058bfc 100644
--- a/arch/arm/kernel/perf_event_v6.c
+++ b/arch/arm/kernel/perf_event_v6.c
@@ -426,12 +426,12 @@ armv6pmu_enable_event(struct hw_perf_event *hwc,
=09 * Mask out the current event and set the counter to count the event
=09 * that we're interested in.
=09 */
-=09spin_lock_irqsave(&pmu_lock, flags);
+=09raw_spin_lock_irqsave(&pmu_lock, flags);
Possibly an Exchange thing? Saving the message body worked and your
hw_breakpoint patches are fine.
Jamie
next prev parent reply other threads:[~2010-12-01 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 17:17 [PATCH] ARM: perf: use raw_spinlock_t for pmu_lock Will Deacon
2010-12-01 16:35 ` Jamie Iles [this message]
2010-12-01 16:45 ` Will Deacon
2010-12-01 17:21 ` Russell King - ARM Linux
2010-12-01 17:23 ` Jamie Iles
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=20101201163547.GE2898@pulham.picochip.com \
--to=jamie@jamieiles.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.