sched: fix rq->clock overflows detection with CONFIG_NO_HZ

Browse source

When using CONFIG_NO_HZ, rq->tick_timestamp is not updated every TICK_NSEC.
We check that the number of skipped ticks matches the clock jump seen in
__update_rq_clock().

Signed-off-by: Guillaume Chazarain <guichaz@yahoo.fr>
Signed-off-by: Ingo Molnar <mingo@elte.hu>

...

This commit is contained in:

Guillaume Chazarain 2008-04-19 19:44:57 +02:00 • committed by Ingo Molnar

parent 30914a58af

commit 15934a3732

1 changed files with 35 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

38

kernel/sched.c

View file