linux-kernel - Re: [PATCH v2] clocksource: atmel-pit: register as a sched

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:	Wed, 24 Feb 2016 17:20:46 +0100
From:	Sylvain Rochet <sylvain.rochet@...secur.com>
To:	Romain Izard <romain.izard.pro@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Boris Brezillon <boris.brezillon@...e-electrons.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2] clocksource: atmel-pit: register as a sched_clock

Hi,

On Wed, Feb 24, 2016 at 05:04:42PM +0100, Romain Izard wrote:
> Register the counter of the Periodic Interval Timer as a possible source
> for sched_clock. Keep the timer running even if the related clockevent
> is disabled.
> 
> This provides a better precision than the jiffies-based default. The
> TCB clocksource does not work, as it is registered too late in the
> initialization sequence.

I have mixed feelings about that, but this is probably just a 
misunderstanding from my part.

The PIT timer should not be used for systems with PM_SUSPEND enabled and 
used because it takes ages to synchronize on resume, how does this patch 
affect that ?

Ref: commit ac34ad27fc ("clockevents: Do not suspend/resume if unused")

Sylvain