linux-kernel - Re: [PATCH] ia64: fix clock_getre(CLOCK

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]

Message-Id: <20220817122103.ecbd08bd545385e5bf8e0d72@linux-foundation.org>
Date:   Wed, 17 Aug 2022 12:21:03 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Sergei Trofimovich <slyich@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org
Subject: Re: [PATCH] ia64: fix clock_getre(CLOCK_MONOTONIC) to report ITC
 frequency

On Mon, 15 Aug 2022 06:49:44 +0100 Sergei Trofimovich <slyich@...il.com> wrote:

> clock_gettime(CLOCK_MONOTONIC, &tp) is very precise on ia64 as it uses
> ITC (similar to rdtsc on x86). It's not quite a hrtimer as it is a few
> times slower than 1ns. Usually 2-3ns.
> 
> clock_getres(CLOCK_MONOTONIC, &res) never reflected that fact and
> reported 0.04s precision (1/HZ value).
> 
> In https://bugs.gentoo.org/596382 gstreamer's test suite failed loudly
> when it noticed precision discrepancy.
> 
> Before the change:
> 
>     clock_getres(CLOCK_MONOTONIC, &res) reported 250Hz precision.
> 
> After the change:
> 
>     clock_getres(CLOCK_MONOTONIC, &res) reports ITC (400Mhz) precision.
> 
> The patch is based on matoro's fix. It adds a bit of explanation why we
> need to special-case arch-specific clock_getres().
> 

It would be best (and nice) to include the original developer's
Signed-off-by: and to Cc Émeric Maschino if possible?

Could you please take care of these paperwork issues?