linux-kernel - Re: [PATCH v6 3/5] clocksource: stm32: only use 32 bits timers

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: <alpine.DEB.2.20.1710182032170.2477@nanos>
Date:   Wed, 18 Oct 2017 20:35:51 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Benjamin Gaignard <benjamin.gaignard@...aro.org>
cc:     robh+dt@...nel.org, mark.rutland@....com, linux@...linux.org.uk,
        mcoquelin.stm32@...il.com, alexandre.torgue@...com,
        daniel.lezcano@...aro.org, ludovic.barre@...com,
        julien.thierry@....com, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 3/5] clocksource: stm32: only use 32 bits timers

On Wed, 18 Oct 2017, Benjamin Gaignard wrote:

> 16 bits hardware are not enough accure to be used.

That should probably read:

  16 bit counters are not accurate enough to be used.

Right?

> Do no allow them to be probed by tested max counter value.

I really do not understand why you want to do this. Accuracy is not really
a reason to dismiss working hardware right away. What you can do is to
lower the rating so other eventually available hardware will be preferred.

I might be missing something, but if so this is obviously missing in the
changelog.

Thanks,

	tglx