Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1547243

Re: [PATCH] nohz: Fix collision between tick and other hrtimers

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Sat, 2016-12-24 at 17:15 +0100, Frederic Weisbecker wrote:
> When the tick is stopped and an interrupt occurs afterward, we check
> on
> that interrupt exit if the next tick needs to be rescheduled. If it
> doesn't need any update, we don't want to do anything.
> 
> In order to check if the tick needs an update, we compare it against
> the
> clockevent device deadline. Now that's a problem because the
> clockevent
> device is at a lower level than the tick itself if it is implemented
> on top of hrtimer.

Ohhhhh, good find. That is one subtle bug.

Acked-by: Rik van Riel <riel@redhat.com>

-- 
All Rights Reversed.

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH] nohz: Fix collision between tick and other hrtimers Frederic Weisbecker <fweisbec@gmail.com> - 2016-12-24 17:20 +0100
  Re: [PATCH] nohz: Fix collision between tick and other hrtimers Rik van Riel <riel@redhat.com> - 2016-12-26 04:00 +0100
    Re: [PATCH] nohz: Fix collision between tick and other hrtimers Frederic Weisbecker <fweisbec@gmail.com> - 2016-12-26 17:50 +0100
  Re: [PATCH] nohz: Fix collision between tick and other hrtimers Wanpeng Li <kernellwp@gmail.com> - 2016-12-27 00:50 +0100
  Re: [PATCH] nohz: Fix collision between tick and other hrtimers Thomas Gleixner <tglx@linutronix.de> - 2016-12-29 17:50 +0100
    Re: [PATCH] nohz: Fix collision between tick and other hrtimers Frederic Weisbecker <fweisbec@gmail.com> - 2016-12-29 18:00 +0100

csiph-web