Re: [PATCH 1/2] nohz: Fix again collision between tick and other hrtimers

From	Rik van Riel <riel@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH 1/2] nohz: Fix again collision between tick and other hrtimers
Date	2017-04-20 18:10 +0200
Message-ID	<tymOD-2ES-27@gated-at.bofh.it> (permalink)
References	<tymlz-2fX-3@gated-at.bofh.it> <tymlz-2fX-1@gated-at.bofh.it>
Organization	Red Hat, Inc

Show all headers | View raw

On Thu, 2017-04-20 at 17:30 +0200, Frederic Weisbecker wrote:
> (This restores commit 24b91e360ef521a2808771633d76ebc68bd5604b that
> got
> reverted by commit 558e8e27e73f53f8a512485be538b07115fe5f3c due to a
> regression where CPUs spuriously stopped ticking. The issue happened
> when a tick fired too early past its expected expiration: on IRQ exit
> the tick was scheduled again to the same deadline but skipped
> reprogramming because ts->next_tick still kept in cache the deadline.
> This has been fixed now with resetting ts->next_tick from the tick
> itself. Extra care has also been taken to prevent from obsolete
> values
> throughout CPU hotplug operations.)
> 
Acked-by: Rik van Riel <riel@redhat.com>

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

Thread

[PATCH 1/2] nohz: Fix again collision between tick and other hrtimers Frederic Weisbecker <fweisbec@gmail.com> - 2017-04-20 17:40 +0200
  Re: [PATCH 1/2] nohz: Fix again collision between tick and other  hrtimers Rik van Riel <riel@redhat.com> - 2017-04-20 18:10 +0200

csiph-web