aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2007-02-28 23:12:19 -0500
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-03-01 17:53:37 -0500
commitc1e16aa2792a129d8920e22210ef21eb62a0f80a (patch)
treebb924b7c77760d01aae19bc6caf1d24869b25e41 /kernel
parentae73fc093a8cae4d92e22ab8b635e3590e80785d (diff)
[PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value
Problem description at: http://bugzilla.kernel.org/show_bug.cgi?id=8048 Commit b18ec80396834497933d77b81ec0918519f4e2a7 [PATCH] sched: improve migration accuracy optimized the scheduler time calculations, but broke posix-cpu-timers. The problem is that the p->last_ran value is not updated after a context switch. So a subsequent call to current_sched_time() calculates with a stale p->last_ran value, i.e. accounts the full time, which the task was scheduled away. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Ingo Molnar <mingo@elte.hu> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel')
-rw-r--r--kernel/sched.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/sched.c b/kernel/sched.c
index 0dc757246d89..0c5ebf59b8bc 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -3566,7 +3566,7 @@ switch_tasks:
3566 3566
3567 sched_info_switch(prev, next); 3567 sched_info_switch(prev, next);
3568 if (likely(prev != next)) { 3568 if (likely(prev != next)) {
3569 next->timestamp = now; 3569 next->timestamp = next->last_ran = now;
3570 rq->nr_switches++; 3570 rq->nr_switches++;
3571 rq->curr = next; 3571 rq->curr = next;
3572 ++*switch_count; 3572 ++*switch_count;