sched: Fix hrtick_start() on UP
The commit177ef2a631
("sched/deadline: Fix a precision problem in the microseconds range") forgot to change the UP version of hrtick_start(), do so now. Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com> Fixes:177ef2a631
("sched/deadline: Fix a precision problem in the microseconds range") [ Fixed the changelog. ] Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Juri Lelli <juri.lelli@arm.com> Cc: Kirill Tkhai <ktkhai@parallels.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Link: http://lkml.kernel.org/r/1416962647-76792-7-git-send-email-wanpeng.li@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
Родитель
75381608e8
Коммит
868933359a
|
@ -492,6 +492,11 @@ static __init void init_hrtick(void)
|
||||||
*/
|
*/
|
||||||
void hrtick_start(struct rq *rq, u64 delay)
|
void hrtick_start(struct rq *rq, u64 delay)
|
||||||
{
|
{
|
||||||
|
/*
|
||||||
|
* Don't schedule slices shorter than 10000ns, that just
|
||||||
|
* doesn't make sense. Rely on vruntime for fairness.
|
||||||
|
*/
|
||||||
|
delay = max_t(u64, delay, 10000LL);
|
||||||
__hrtimer_start_range_ns(&rq->hrtick_timer, ns_to_ktime(delay), 0,
|
__hrtimer_start_range_ns(&rq->hrtick_timer, ns_to_ktime(delay), 0,
|
||||||
HRTIMER_MODE_REL_PINNED, 0);
|
HRTIMER_MODE_REL_PINNED, 0);
|
||||||
}
|
}
|
||||||
|
|
Загрузка…
Ссылка в новой задаче