linux-kernel - Re: [PATCH v2 3/3] tracing: Add documentation for trace clock tai

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 14 Apr 2022 18:27:07 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Kurt Kanzenbach <kurt@...utronix.de>,
        John Stultz <john.stultz@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Stephen Boyd <sboyd@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>,
        Jonathan Corbet <corbet@....net>
Cc:     Richard Cochran <richardcochran@...il.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] tracing: Add documentation for trace clock tai

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