Hi Thomas,
The tick reschedules itself unconditionally. That's what we want as long
as the CPU is in periodic mode. It's not that relevant when the CPU
is in dynticks mode though as the clock write is likely to be overwritten
by the nohz code on irq exit.
In low-res mode, that even result in unexpected periodic behaviour when
no timer is scheduled in the future.
So here is a set that proposes the removal of these double writes.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
origin/nohz/drop-double-write-v2
Thanks,
Frederic
---
Viresh Kumar (2):
nohz: Fix spurious periodic tick behaviour in low-res dynticks mode
nohz: Avoid tick's double reprogramming in highres mode
kernel/time/tick-sched.c | 8 ++++++++
1 file changed, 8 insertions(+)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
