From: Thomas Gleixner <tglx@linutronix.de>
To: Joel Fernandes <joelaf@google.com>
Cc: Ingo Molnar <mingo@kernel.org>,
John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCH 7/7] trace: Update documentation for mono, mono_raw and boot clock
Date: Tue, 29 Nov 2016 17:11:15 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1611291710490.4358@nanos> (raw)
In-Reply-To: <CAJWu+opzu=J0=6FJvVQUWuQ1frzcJxRtADxp4ULZ_e1pm6bFUA@mail.gmail.com>
On Tue, 29 Nov 2016, Joel Fernandes wrote:
> On Mon, Nov 28, 2016 at 11:26 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * John Stultz <john.stultz@linaro.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, I'll fix these up and repost.
Don't bother. I have fixed it up locally already.
Thanks,
tglx
next prev parent reply other threads:[~2016-11-29 16:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 22:35 [GIT PULL][PATCH 0/7] Timekeeping changes for 4.10 (take 2) John Stultz
2016-11-28 22:35 ` [PATCH 1/7] selftests/timers: Fix spelling mistake "Asyncrhonous" -> "Asynchronous" John Stultz
2016-11-29 17:10 ` [tip:timers/core] " tip-bot for Colin Ian King
2016-11-28 22:35 ` [PATCH 2/7] timekeeping: Ignore the bogus sleep time if pm_trace is enabled John Stultz
2016-11-29 7:19 ` Ingo Molnar
2016-11-29 9:38 ` Chen Yu
2016-11-29 17:10 ` [tip:timers/core] " tip-bot for Chen Yu
2016-11-28 22:35 ` [PATCH 3/7] timekeeping: clocksource_cyc2ns: Document intended range limitation John Stultz
2016-11-29 17:11 ` [tip:timers/core] timekeeping/clocksource_cyc2ns: " tip-bot for Chris Metcalf
2016-11-28 22:35 ` [PATCH 4/7] time: alarmtimer: Add the tracepoints for alarmtimer John Stultz
2016-11-29 7:23 ` Ingo Molnar
2016-11-29 8:23 ` Baolin Wang
2016-11-29 9:12 ` Ingo Molnar
2016-11-29 11:52 ` Baolin Wang
2016-11-29 12:06 ` Thomas Gleixner
2016-11-30 11:43 ` Baolin Wang
2016-12-01 2:34 ` Baolin Wang
2016-12-01 13:52 ` [tip:timers/core] alarmtimer: Add tracepoints for alarm timers tip-bot for Baolin Wang
2016-11-28 22:35 ` [PATCH 5/7] timekeeping: Add a fast and NMI safe boot clock John Stultz
2016-11-29 17:11 ` [tip:timers/core] " tip-bot for Joel Fernandes
2016-11-28 22:35 ` [PATCH 6/7] trace: Add an option for boot clock as trace clock John Stultz
2016-11-28 23:05 ` Steven Rostedt
2016-11-29 17:12 ` [tip:timers/core] " tip-bot for Joel Fernandes
2016-11-28 22:35 ` [PATCH 7/7] trace: Update documentation for mono, mono_raw and boot clock John Stultz
2016-11-28 23:07 ` Steven Rostedt
2016-11-29 7:26 ` Ingo Molnar
2016-11-29 16:10 ` Joel Fernandes
2016-11-29 16:11 ` Thomas Gleixner [this message]
2016-11-29 17:13 ` [tip:timers/core] " tip-bot for Joel Fernandes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1611291710490.4358@nanos \
--to=tglx@linutronix.de \
--cc=joelaf@google.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®