Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Message-ID: <0dd9ba0e-712a-37f6-a50d-f5510cd23033@gmail.com>
Date:   Thu, 14 Apr 2022 18:27:07 +0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.0
Subject: Re: [PATCH v2 3/3] tracing: Add documentation for trace clock tai
Content-Language: en-US
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
References: <20220414091805.89667-1-kurt@linutronix.de>
 <20220414091805.89667-4-kurt@linutronix.de>
From:   Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <20220414091805.89667-4-kurt@linutronix.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

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