linux-kernel - Re: [PATCH] sparc/time: set ->min_delta_ticks and ->max_delta

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: <20170401.121850.1228750723867716615.davem@davemloft.net>
Date:   Sat, 01 Apr 2017 12:18:50 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     nicstange@...il.com
Cc:     john.stultz@...aro.org, linux-kernel@...r.kernel.org,
        tglx@...utronix.de, sparclinux@...r.kernel.org
Subject: Re: [PATCH] sparc/time: set ->min_delta_ticks and ->max_delta_ticks

From: Nicolai Stange <nicstange@...il.com>
Date: Thu, 30 Mar 2017 21:56:47 +0200

> In preparation for making the clockevents core NTP correction aware,
> all clockevent device drivers must set ->min_delta_ticks and
> ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a
> clockevent device's rate is going to change dynamically and thus, the
> ratio of ns to ticks ceases to stay invariant.
> 
> Make the sparc arch's clockevent drivers initialize these fields properly.
> 
> This patch alone doesn't introduce any change in functionality as the
> clockevents core still looks exclusively at the (untouched) ->min_delta_ns
> and ->max_delta_ns. As soon as this has changed, a followup patch will
> purge the initialization of ->min_delta_ns and ->max_delta_ns from these
> drivers.
> 
> Signed-off-by: Nicolai Stange <nicstange@...il.com>

Acked-by: David S. Miller <davem@...emloft.net>