From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kurt Kanzenbach <kurt@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>
Cc: Richard Cochran <richardcochran@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] tracing: Add documentation for trace clock tai
Date: Thu, 14 Apr 2022 18:27:07 +0700 [thread overview]
Message-ID: <0dd9ba0e-712a-37f6-a50d-f5510cd23033@gmail.com> (raw)
In-Reply-To: <20220414091805.89667-4-kurt@linutronix.de>
On 4/14/22 16:18, Kurt Kanzenbach wrote:
> + tai:
> + This is the tai clock (CLOCK_TAI) and is derived from the wall-
> + clock time. However, this clock does not experience
> + discontinuities and backwards jumps caused by NTP inserting leap
> + seconds. Since the clock access is designed for use in tracing,
> + side effects are possible. The clock access may yield wrong
> + readouts in case the internal TAI offset is updated e.g., caused
> + by setting the system time or using adjtimex() with an offset.
> + These effects are rare and post processing should be able to
> + handle them. See comments in the ktime_get_tai_fast_ns()
> + function for more information.
> +
In what file are the ktime_get_tai_fast_ns() comments?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-14 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 9:18 [PATCH v2 0/3] tracing: Introduce trace clock tai Kurt Kanzenbach
2022-04-14 9:18 ` [PATCH v2 1/3] timekeeping: Introduce fast accessor to " Kurt Kanzenbach
2022-04-14 14:59 ` Thomas Gleixner
2022-04-18 17:15 ` Steven Rostedt
2022-04-14 15:01 ` [tip: timers/core] " tip-bot2 for Kurt Kanzenbach
2022-04-26 21:53 ` [PATCH v2 1/3] " Steven Rostedt
2022-04-27 8:17 ` Thomas Gleixner
2022-04-27 8:38 ` Kurt Kanzenbach
2022-04-27 15:27 ` Steven Rostedt
2022-04-27 17:22 ` Steven Rostedt
2022-04-27 19:23 ` Steven Rostedt
2022-04-27 20:06 ` Thomas Gleixner
2022-04-27 20:08 ` Steven Rostedt
2022-04-27 20:42 ` Kurt Kanzenbach
2022-04-27 21:05 ` Steven Rostedt
2022-04-27 21:12 ` Thomas Gleixner
2022-04-14 9:18 ` [PATCH v2 2/3] tracing: Introduce trace " Kurt Kanzenbach
2022-04-14 9:18 ` [PATCH v2 3/3] tracing: Add documentation for " Kurt Kanzenbach
2022-04-14 11:27 ` Bagas Sanjaya [this message]
2022-04-14 11:38 ` Kurt Kanzenbach
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=0dd9ba0e-712a-37f6-a50d-f5510cd23033@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=john.stultz@linaro.org \
--cc=kurt@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.