Messages in this thread | | | Subject | Re: [PATCH 2/2] tick: Make sure tick timer is active when bypassing reprogramming | From | Rik van Riel <> | Date | Thu, 20 Apr 2017 12:01:25 -0400 |
| |
On Thu, 2017-04-20 at 17:30 +0200, Frederic Weisbecker wrote: > So far we have run into too much troubles with the optimization path > that skips reprogramming the clock on IRQ exit when the expiration > deadline hasn't changed. If by accident the cached deadline happens > to > be out of sync with the hardware deadline, the buggy result and its > cause are hard to investigate. So lets detect and warn about the > issue > early. > > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> > Cc: Tim Wright <tim@binbash.co.uk> > Cc: Pavel Machek <pavel@ucw.cz> > Cc: James Hartsock <hartsjc@redhat.com> > Cc: Peter Zijlstra <peterz@infradead.org> > Cc: Rik van Riel <riel@redhat.com> > Cc: Thomas Gleixner <tglx@linutronix.de> > Cc: Ingo Molnar <mingo@kernel.org>
Acked-by: Rik van Riel <riel@redhat.com>
| |