Srivatsa Vaddagiri
authored
Enabling SCHED_HRTICK currently results in rq->lock recursion and a hard
hang at bootup. Essentially try_to_wakeup() grabs rq->lock and tries
arming a hrtimer via hrtimer_restart(), which deep down tries waking up
ksoftirqd, which leads to a recursive call to try_to_wakeup() and thus
attempt to take rq->lock recursively!!
This is fixed by having scheduler queue hrtimer via
__hrtimer_start_range_ns() which avoids waking up ksoftirqd.
Signed-off-by:
Srivatsa Vaddagiri <vatsa@codeaurora.org>
Change-Id: I11a13be1d9db3a749614ccf3d4f5fb7bf6f18fa1
Name | Last commit | Last update |
---|---|---|
.. | ||
Makefile | ||
auto_group.c | ||
auto_group.h | ||
clock.c | ||
core.c | ||
cpupri.c | ||
cpupri.h | ||
debug.c | ||
fair.c | ||
features.h | ||
idle_task.c | ||
rt.c | ||
sched.h | ||
sched_avg.c | ||
stats.c | ||
stats.h | ||
stop_task.c |