From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932401AbcHXJk2 (ORCPT ); Wed, 24 Aug 2016 05:40:28 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:33933 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754726AbcHXJk0 (ORCPT ); Wed, 24 Aug 2016 05:40:26 -0400 From: Nicolai Stange To: Nicolai Stange Cc: Thomas Gleixner , John Stultz , linux-kernel@vger.kernel.org Subject: Re: [RFC v4 22/22] timekeeping: inform clockevents about freq adjustments References: <20160822233320.4548-1-nicstange@gmail.com> <20160822233320.4548-23-nicstange@gmail.com> Date: Wed, 24 Aug 2016 11:40:23 +0200 In-Reply-To: <20160822233320.4548-23-nicstange@gmail.com> (Nicolai Stange's message of "Tue, 23 Aug 2016 01:33:20 +0200") Message-ID: <877fb61p4o.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Nicolai Stange writes: > --- a/kernel/time/timekeeping.c > +++ b/kernel/time/timekeeping.c > @@ -1845,6 +1845,9 @@ static __always_inline void timekeeping_apply_adjustment(struct timekeeper *tk, > tk->xtime_interval += interval; > tk->tkr_mono.xtime_nsec -= offset; > tk->ntp_error -= (interval - offset) << tk->ntp_error_shift; > + > + clockevents_adjust_all_freqs(tk->tkr_mono.mult, > + tk->tkr_mono.clock->mult); > } FYI, the kernel build robot has reported a build failure for CONFIG_GENERIC_CLOCKEVENTS=n. In order to avoid unnecessary traffic, I'll only fix this up in a v5 if you give the whole thing a go.