[PATCH 1/9] perf_counter: fix NMI race in task clock

From: Peter Zijlstra
Date: Wed Apr 08 2009 - 09:06:18 EST


We should not be updating ctx->time from NMI context, work around that.

Signed-off-by: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
---
kernel/perf_counter.c | 25 ++++++++++++++++---------
1 file changed, 16 insertions(+), 9 deletions(-)

Index: linux-2.6/kernel/perf_counter.c
===================================================================
--- linux-2.6.orig/kernel/perf_counter.c
+++ linux-2.6/kernel/perf_counter.c
@@ -319,8 +319,6 @@ static void __perf_counter_disable(void

spin_lock_irqsave(&ctx->lock, flags);

- update_context_time(ctx);
-
/*
* If the counter is on, turn it off.
* If it is in error state, leave it in error state.
@@ -2335,13 +2333,11 @@ static const struct hw_perf_counter_ops
* Software counter: task time clock
*/

-static void task_clock_perf_counter_update(struct perf_counter *counter)
+static void task_clock_perf_counter_update(struct perf_counter *counter, u64 now)
{
- u64 prev, now;
+ u64 prev;
s64 delta;

- now = counter->ctx->time;
-
prev = atomic64_xchg(&counter->hw.prev_count, now);
delta = now - prev;
atomic64_add(delta, &counter->count);
@@ -2369,13 +2365,24 @@ static int task_clock_perf_counter_enabl
static void task_clock_perf_counter_disable(struct perf_counter *counter)
{
hrtimer_cancel(&counter->hw.hrtimer);
- task_clock_perf_counter_update(counter);
+ task_clock_perf_counter_update(counter, counter->ctx->time);
+
}

static void task_clock_perf_counter_read(struct perf_counter *counter)
{
- update_context_time(counter->ctx);
- task_clock_perf_counter_update(counter);
+ u64 time;
+
+ if (!in_nmi()) {
+ update_context_time(counter->ctx);
+ time = counter->ctx->time;
+ } else {
+ u64 now = perf_clock();
+ u64 delta = now - counter->ctx->timestamp;
+ time = counter->ctx->time + delta;
+ }
+
+ task_clock_perf_counter_update(counter, time);
}

static const struct hw_perf_counter_ops perf_ops_task_clock = {

--

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/