From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f43.google.com ([74.125.82.43]:36426 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbdE3FrN (ORCPT ); Tue, 30 May 2017 01:47:13 -0400 Date: Tue, 30 May 2017 07:47:09 +0200 From: Ingo Molnar To: Frederic Weisbecker Cc: LKML , Peter Zijlstra , Rik van Riel , James Hartsock , Thomas Gleixner , stable@vger.kernel.org, Tim Wright , Pavel Machek Subject: Re: [PATCH 0/2] nohz: Deal with clock reprogram skipping issues v3 Message-ID: <20170530054709.hth3myap4mq5zvcp@gmail.com> References: <1495201910-12466-1-git-send-email-fweisbec@gmail.com> <20170523072508.3bzyipgwnyjcbef6@gmail.com> <20170523131042.GA26103@lerouge> <20170524071628.ftwjuh27jpdo6qkm@gmail.com> <20170526021051.GA27061@lerouge> <20170526061320.uhl34walndqv6wo6@gmail.com> <20170529135541.GA8425@lerouge> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170529135541.GA8425@lerouge> Sender: stable-owner@vger.kernel.org List-ID: * Frederic Weisbecker wrote: > > Well, this does not answer my question: between latest tip:timers/nohz and the > > patches you posted there's a delta, so it's not just a pure rebase. > > Yeah but like I said, you can forget the series I posted because the diff is > mostly cosmetic and things are actually ok as they are in tip:timers/nohz > > The only thing that bothers me is the fact that the HEAD of this branch doesn't have > a changelog or even just a comment. We can still amend that - is this changelog what you had in mind: nohz: Reset next_tick cache even when the timer has no regs Handle tick interrupts whose regs are NULL, out of general paranoia. It happens when hrtimer_interrupt() is called from non-interrupt contexts, such as hotplug CPU down events. ? Or you can send me a longer version as well. Thanks, Ingo