diff options
| author | KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> | 2013-05-26 17:35:41 -0400 |
|---|---|---|
| committer | Frederic Weisbecker <fweisbec@gmail.com> | 2013-07-04 18:02:30 +0200 |
| commit | fa18f7bde3ad4568d1d343b60d963bfbd8dc3991 (patch) | |
| tree | aa51270ce1fcc53f2547571b615a53e4e1bce464 /init/Kconfig | |
| parent | a0b2062b0904ef07944c4a6e4d0f88ee44f1e9f2 (diff) | |
posix-cpu-timers: don't account cpu timer after stopped thread runtime accounting
When tsk->signal->cputimer->running is 1, signal->cputimer (i.e. per process
timer account) and tsk->sum_sched_runtime (i.e. per thread timer account)
increase at the same pace because update_curr() increases both accounting.
However, there is one exception. When thread exiting, __exit_signal() turns
over task's sum_shced_runtime to sig->sum_sched_runtime, but it doesn't stop
signal->cputimer accounting.
This inconsistency makes POSIX timer wake up too early. This patch fixes it.
Original-patch-by: Olivier Langlois <olivier@trillion01.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Olivier Langlois <olivier@trillion01.com>
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Diffstat (limited to 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions