Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756300AbcK2H1E (ORCPT ); Tue, 29 Nov 2016 02:27:04 -0500 Received: from mail-wj0-f193.google.com ([209.85.210.193]:35886 "EHLO mail-wj0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755840AbcK2H0z (ORCPT ); Tue, 29 Nov 2016 02:26:55 -0500 Date: Tue, 29 Nov 2016 08:26:51 +0100 From: Ingo Molnar To: John Stultz Cc: lkml , Joel Fernandes , Steven Rostedt , Thomas Gleixner , Ingo Molnar , Richard Cochran , Prarit Bhargava Subject: Re: [PATCH 7/7] trace: Update documentation for mono, mono_raw and boot clock Message-ID: <20161129072651.GD29412@gmail.com> References: <1480372524-15181-1-git-send-email-john.stultz@linaro.org> <1480372524-15181-8-git-send-email-john.stultz@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1480372524-15181-8-git-send-email-john.stultz@linaro.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 909 Lines: 21 * John Stultz wrote: > + boot: This is the boot clock (CLOCK_BOOTTIME) and is based on the > + fast monotonic clock, but also accounts for time spent in > + suspend. Since the clock access is designed for use in > + tracing in the suspend path, some side effects are possible > + if clock is accessed after the suspend time is accounted before > + the fast mono clock is updated. In this case, the clock update > + appears to happen slightly sooner than it normally would have. > + Also on 32-bit systems, its possible that the 64-bit boot offset > + sees a partial update. These effects are rare and post > + processing should be able to handle them. See comments on > + ktime_get_boot_fast_ns function for more information. s/its possible/it's possible s/comments on ktime_get_boost_fast_ns function/comments in the ktime_get_boost_fast_ns() function Thanks, Ingo