linux-kernel - Re: [RFC v4 10/22] arch/tile/kernel/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: <262d7903-f31e-bc93-fcb9-0530b9f4d414@mellanox.com>
Date:   Tue, 6 Sep 2016 15:19:31 -0400
From:   Chris Metcalf <cmetcalf@...lanox.com>
To:     Nicolai Stange <nicstange@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>
CC:     John Stultz <john.stultz@...aro.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [RFC v4 10/22] arch/tile/kernel/time: set ->min_delta_ticks and
 ->max_delta_ticks

On 08/22/2016 07:33 PM, Nicolai Stange wrote:
> With the yet to come introduction of NTP correction awareness to the
> clockevent core, drivers should report their valid ranges in units of
> cycles to the latter.
>
> Currently, the tile's timer clockevent device is initialized as follows:
>
>   evt->max_delta_ns = clockevent_delta2ns(MAX_TICK, evt);
>
> and
>
>   .min_delta_ns = 1000,
>
> The first one translates to a ->max_delta_ticks value of MAX_TICK.
> For the latter, note that the clockevent core will superimpose a
> minimum of 1us by itself -- setting ->min_delta_ticks to 1 is safe here.
>
> Initialize ->min_delta_ticks and ->max_delta_ticks with these values.
>
> Signed-off-by: Nicolai Stange <nicstange@...il.com>
> ---
>  arch/tile/kernel/time.c | 2 ++
>  1 file changed, 2 insertions(+)

Thanks.  Taken into the tile tree.
-- 
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com