Re: [PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-03-01 Thread Andrew Morton
On Thu, 01 Mar 2007 18:45:14 -0500 Chuck Ebbert <[EMAIL PROTECTED]> wrote: > Thomas Gleixner wrote: > > Problem description at: > > http://bugzilla.kernel.org/show_bug.cgi?id=8048 > > > > Commit b18ec80396834497933d77b81ec0918519f4e2a7 > > [PATCH] sched: improve migration accuracy > > optimi

Re: [PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-03-01 Thread Chuck Ebbert
Thomas Gleixner wrote: > 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

Re: [PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-02-22 Thread John
Thomas Gleixner wrote: 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_

Re: [PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-02-22 Thread Mike Galbraith
On Thu, 2007-02-22 at 01:33 +0100, Thomas Gleixner wrote: > 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-cp

Re: [PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-02-21 Thread Thomas Gleixner
On Thu, 2007-02-22 at 08:46 +0100, Ingo Molnar wrote: > * Thomas Gleixner <[EMAIL PROTECTED]> wrote: > > > 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. account

Re: [PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-02-21 Thread Ingo Molnar
* Thomas Gleixner <[EMAIL PROTECTED]> wrote: > 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. > > Sig

[PATCH] Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-02-21 Thread Thomas Gleixner
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 af