[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161129072651.GD29412@gmail.com>
Date: Tue, 29 Nov 2016 08:26:51 +0100
From: Ingo Molnar <mingo@...nel.org>
To: John Stultz <john.stultz@...aro.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Joel Fernandes <joelaf@...gle.com>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Richard Cochran <richardcochran@...il.com>,
Prarit Bhargava <prarit@...hat.com>
Subject: Re: [PATCH 7/7] trace: Update documentation for mono, mono_raw and
boot clock
* John Stultz <john.stultz@...aro.org> 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
Powered by blists - more mailing lists